One note held against a contact
One note: id, title, body, and the ISO-8601 instants it was written and last changed.
The note is found by note_id alone. contact_id is in the path because the note belongs to a contact, but it is not part of the lookup, so a note id paired with the wrong contact still answers that note. Do not read a 200 here as proof that the note belongs to the contact you named.
A note id nothing has is refused 404. get_contact_notes is the door when the whole list is wanted, and the only one that answers which notes a contact really holds.
Scope: suppliers:read.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/contacts/{contact_id}/notes/{note_id}
- Auth: HTTP bearer
Path parameters
The contact's id, a whole number, as list_contacts serves it.
The note's id, a whole number, as get_contact_notes 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 note as it stands.
Changes
No recorded changes to this operation across all 1 revision of this API.