Write a note against a contact
Writes one note against a contact and answers 201 with it, including the id and the two instants.
title and body are both required. title is capped at 200 characters and body at 200 words, counted on whitespace. A note is a line somebody reads beside a contact, not a document.
The contact id is not read before the write, but the note's foreign key is: an id no contact has fails the call rather than storing an orphan, and today that surfaces as a 500 rather than a 404. Read the contact first where the id did not come from a Tightly read.
A note is append-only from this door: update_contact_note is what changes one that exists.
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
- 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.
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 written, with its id and both instants.
Changes
No recorded changes to this operation across all 1 revision of this API.