# PATCH /api/v2/notes/{note}

Update a note

- MCP id: notes.update
- Scope: api:write:project_drive
- Scope: api:write:customer_drive
- Scope: api:write:organization_drive
- Scope: api:write:user_drive
- Permission: project_drive::create
- Rate cost: 1 unit, write bucket. A write costs the same whatever `view` you ask for.
- Cache-Control: private, no-store

Partially updates a note: absent keys are untouched, an empty body is rejected.

`content` is the only writable key: a note cannot be re-parented, so neither half of the notable pair is accepted, matching plnnrly, whose only per-note edit action writes the body. Editing needs the parent's note permission (`projects::notes`, `customers::update` or `project_management::manage_work_items` by parent type), or the request is `403` `forbidden-by-policy`. Writing a note touches its parent record's `updated_at`. Send `If-Match` with the `ETag` from your last read to detect a concurrent edit, which answers `412`. Treat it as best-effort only: this resource carries no concurrency token and `updated_at` is second-precision, so two writes inside the same second are indistinguishable. The declared permission is `project_drive::create` (editing is part of the create permission), and the other three drive prefixes apply by owner type.

## Parameters
- note (integer, path): The Note's numeric id.
- view (string, optional): Which field set to render.
- X-Request-Id (header, optional): A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.
- If-Match (header, optional): The ETag a write is conditional on. A stale validator is 412 precondition-failed.

## Request body
- content (string ≤ 500000, optional): Note body as rich-text HTML, sanitised on read.

Unknown keys are refused with `422` validation-failed, naming the key.

## Response 200
- id (integer, required): Unique identifier.
- content (html, required): Note body as rich-text HTML, sanitised on read.
- order_column (integer, required, server-assigned): Sort position within the parent record. Assigned by the server; reordering is not exposed in v2.0. Positions are not counted per parent, so the sequence is effectively creation order across the whole organisation.
- user_id (integer or null, required, server-assigned): Author of the note. Always the authenticated user at create time; `null` where the author has since been deleted.
- created_at (timestamp (YYYY-MM-DDThh:mm:ssZ), required): Creation timestamp.
- updated_at (timestamp (YYYY-MM-DDThh:mm:ssZ), required): Last-write timestamp; use for incremental sync.
- notable_type (string, required): The kind of record `notable` points at; it says which branch of `notable` applies.
- notable_id (integer, required): The id of the record `notable` points at.
- notable (Ref or ProjectSummary or CustomerSummary or WorkItemSummary, required): The project, customer or work item this note is attached to.
- user (Ref or UserSummary or null, required): Author of the note.
- links (NoteLinks, required)
  - self (url, required): The canonical URI of this record.

## Errors
- 403 forbidden-by-policy | insufficient-permission | insufficient-token-scope: Forbidden.
- 412 precondition-failed: Precondition failed.
- 415 unsupported-media-type: Unsupported media type.
- 422 unprocessable-relationship | validation-failed: Unprocessable content.
- 400 idempotency-key-required | invalid-cursor | invalid-query-parameter | malformed-request | unsupported-parameter: Bad request.
- 401 token-expired | unauthenticated: Unauthenticated.
- 404 endpoint-not-found | resource-not-found: Not found.
- 406 not-acceptable: Not acceptable.
- 429 rate-limit-exceeded: Too many requests.
- 500 internal-error: Server error.
- 503 tenant-unavailable: Service unavailable.

## Example
```bash
curl -X PATCH \
  'https://<your-url>/api/v2/notes/1' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'If-Match: *' \
  -d '{
    "content": "<p>Kick-off confirmed for Monday 09:00.</p>"
  }'
```