Change a note held against a contact
Changes one note and answers it whole, with updated_at moved.
title and body are both optional and either can be sent alone. A field left out is untouched, and so is a field sent null, which this door reads as "no change" rather than as "clear it", so a note cannot be emptied through it. The caps are the ones create_contact_note applies: 200 characters of title, 200 words of body.
As on get_contact_note, the note is found by note_id alone and contact_id is not part of the lookup, so a note id paired with the wrong contact is still changed. A note id nothing has is refused 404.
Scope: suppliers:write, which includes 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.
A string of your own, up to 255 characters, that makes this write safe to retry. Send the same key twice and the second request is answered with the first one's status and body instead of writing again, so a client that retried after a timeout ends holding the record's id rather than creating a second one. Reusing a key with a different body, or while the first request is still running, is refused 409. A write that failed releases its key. Keys answer for 24 hours and belong to the API key that used them. A key longer than 255 characters is ignored and the write goes ahead without the guarantee.
Request body
Response
The note as it now stands, with updated_at moved.
Changes
No recorded changes to this operation across all 1 revision of this API.