Skip to main content
PUT
Update Note

Authorizations

Authorization
string
header
required

Org API key as Token token=ei_live_...

Path Parameters

note_id
string
required

Body

application/json

PUT /v1/notes/{id} → topic_notes. Only personal notes are writable; shared notes are read-only over /v1. content_markdown is decoded back into the note's stored sections — an unrecognised section block round-trips untouched. When both fields are sent, title wins over any title in the markdown front matter.

title
string | null
Required string length: 1 - 300
content_markdown
string | null
Maximum string length: 200000

Response

Successful Response

A topic note. content_markdown is the note's full body as a markdown document (see api.notes_codec) — it is populated on GET /v1/notes/{id} and is null in list responses, which carry metadata only.

scope is derived: 'shared' for the published global corpus, 'personal' for a note owned by the API key's creator. The physical note_type vocabulary and the structured_content JSONB shape are deliberately not exposed.

id
string
required
title
string | null
content_markdown
string | null
topic_id
string | null
scope
enum<string> | null
Available options:
shared,
personal
created_at
string | null
updated_at
string | null