Update a note

PATCH 
/api/v1/notes/:note_id

Update fields on an existing note.

Only fields present in the request body are updated; omitted fields preserve their current value. The updated_at timestamp is refreshed on any mutation.

• Scope required: assessments:update.
• Rate-limit tier: user_mutation (180/hour/user).
• Idempotent per-request; repeated identical payloads are safe.

Request

Responses

200

Successful Response

400

Bad request — malformed input or failed validation.

401

Missing, expired, or invalid credentials.

403

Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.