---
title: "Write a note against a contact"
method: POST
path: "/api/v1/contacts/{contact_id}/notes"
tags: ["contacts"]
---

# Write a note against a contact

`POST /api/v1/contacts/{contact_id}/notes`

## Request

- Base URL: `https://api.app.tightly.io`
- URL: `https://api.app.tightly.io/api/v1/contacts/{contact_id}/notes`
- Auth: HTTP bearer

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`.

## Path parameters

- `contact_id` string, required

## Headers

- `Tightly-Version` string
- `Idempotency-Key` string

## Request body

- CreateContactNoteRequest
  - `body` string, required
  - `title` string, required

## Response `201`

The note as written, with its id and both instants.

- CreateContactNoteResponse
  - `data` union
    - ContactNotePayload
      - `body` string, required
      - `created_at` string, required
      - `id` string, required
      - `title` string, required
      - `updated_at` string, required
    - object, nullable
  - `message` ContactsApiMessage
    - `desc` string
    - `service` string
    - `severity` 'SUCCESS' | 'INFO' | 'ERROR' | 'WARNING'

## Other responses

- `400`: `title` is over 200 characters, `body` is over 200 words, or one of them is missing.
- `401`: No usable key: malformed, unknown, revoked, expired or stopped. One refusal covers all five, telling a caller which is which maps the surface for them. A request with no Authorization header at all is refused 400 before any key is looked for.
- `403`: The key may not reach this operation. `scope_missing` when the key does not hold Suppliers; `ip_not_allowed` when the caller's address is outside the key's allowlist. There is no `organization_mismatch` on this resource: no supplier or contact route names an organisation in its path, so there is nothing for a key to disagree with.
- `429`: The key has spent its allowance for this minute. 600 reads and 120 writes a minute, counted per key, refused calls included. `Retry-After` says how long to wait.
- `503`: The database is briefly out of reach, which is what a failover or a full connection pool looks like from outside. Wait the seconds `Retry-After` names and send the request again. A read is safe to repeat. A write is not, because the connection was lost in the middle of it, so read the object back before sending it a second time. Branch on the status rather than on `code`, which is `POSTGRES_UNAVAILABLE` from one of the two seams that raise this and `SERVICE_UNAVAILABLE` from the other.

---

[API](https://skmtc.dev/tightly/apis/tightly-api.md) · [All operations](https://skmtc.dev/tightly/apis/tightly-api/llms.txt) · [OpenAPI document](https://skmtc.dev/tightly/apis/tightly-api/revisions/199f7eb35afb?raw)