---
title: "Delete a note held against a contact"
method: DELETE
path: "/api/v1/contacts/{contact_id}/notes/{note_id}"
tags: ["contacts"]
---

# Delete a note held against a contact

`DELETE /api/v1/contacts/{contact_id}/notes/{note_id}`

## 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

Deletes one note and answers 204 with no body. The contact is untouched.

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 deleted. A note id nothing has is refused 404, so a second delete of the same note answers 404 rather than 204.

There is no undo, and no soft delete: the row is gone.

Scope: `suppliers:write`, which includes `suppliers:read`.

## Path parameters

- `contact_id` string, required
- `note_id` string, required

## Headers

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

## Response `204`

The note is gone. No body.

## Other responses

- `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.
- `404`: No note has that id.
- `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)