Every note held against one contact
Every note held against one contact, as an array: id, title, body, and the ISO-8601 instants the note was written and last changed. data is the array itself rather than an object wrapping one, and it is empty where the contact has no notes.
There is no paging and no ordering argument: notes come back in the order the database holds them, so sort on created_at where the order matters to a reader.
A contact id no contact has answers an empty array rather than 404, because the notes are looked up by contact id and no contact is read. get_contact is the door that tells you whether the contact exists.
Scope: suppliers:read.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/contacts/{contact_id}/notes
- Auth: HTTP bearer
Path parameters
The contact's id, a whole number, as list_contacts serves it.
Headers
The date train to answer on. One train exists today, 2026-11, the one this reference describes and the one every key is minted on, so the call answers on it with or without this header. Send it anyway, so a client built now names its train from the start.
Response
The contact's notes, newest not guaranteed first. Empty where there are none.
Changes
No recorded changes to this operation across all 1 revision of this API.