For the complete documentation index, see llms.txt. This page is also available as Markdown.

Update Note

Update a note's title, body, parent folder, or object link. This is a partial update — only the fields you send are changed. Replacing note_data records a new entry in the note's version history. To add to the end of a note without replacing it, use append-note.md.

PATCH /v1/notes/{uuid}
Content-Type: application/json

Path parameters

Parameter
Description

uuid

UUID of the note to update.

Request body

At least one field is required.

Field
Type
Description

note_tag

string

New title. Cannot be empty or null.

note_data

string (HTML) or null

Replaces the entire note body. Normalized through the rich-text renderer. null clears the body.

parent_id

string or null

Move the note into another folder (must be a folder in the same case). null moves the note to the case root.

object_id

string

Re-link the note to a different object. Replaces any existing link; requires object_type.

object_type

string

One of timeline_event, task, case, evidence, acquisition.

Example request

{
  "note_tag": "Initial Triage (revised)",
  "note_data": "<h2>Intake</h2><p>Device received, photographed, and bagged.</p>"
}

Response — 200 OK

Returns the updated note with content included (same shape as get-notes.md):

Examples

Rename a note

Replace the note body

Move a note into a folder / back to the root

Errors

Status
Body
Cause

400

{"message": "Invalid request body", "errors": [...]}

No updatable fields sent, empty note_tag, invalid object_type, ...

400

{"message": "Parent note with UUID ... is not a folder"}

parent_id references a regular note (or a folder in another case / a missing note — see create-note.md for all three variants).

404

{"message": "Note not found"}

No note with that UUID.

401

Unauthorized

Missing or invalid API key.

Was this helpful?