Enhance or revise a note
Starts an enhancement using the caller’s existing note-edit authorization.
Supply non-empty instructions, an explicit note_template_id, or both.
With an explicit template, regenerate that template’s enhanced-note entry from
the persisted raw user notes and transcript, applying any supplied instructions.
Without a template, revise the persisted HTML of enhanced_note_id, or the
entry matching last_note_template_id when the target is omitted. Preserve
that entry’s template association. A missing or empty enhanced target is a
400 error; instruction-only requests never fall back to raw notes.
operation_id makes retries idempotent within this note. Reusing an ID with
different input is a 409 error. A replay returns the existing operation,
including its durable result when completed. A different operation while
one is running returns 409. expected_revision, when supplied, must match
the note’s current revision. Otherwise the current revision is captured.
The final write must still match that captured revision; a concurrent edit
fails the operation with an error whose code is 409 and leaves that edit intact.
The operation continues if the client disconnects. A 200 response contains its terminal snapshot; a 202 response contains a still-running snapshot. Attach to GET on this endpoint to observe progress or recover after reconnect.
instructions to revise existing saved enhanced HTML, note_template_id to regenerate from raw user notes and transcript, or both. Read the note first and supply its revision as expected_revision. Raw notes, transcript, and the template remain unchanged.
A 200 response contains a terminal snapshot; 202 means the operation is still running. Only enhancement.status: completed with enhancement.ai_note confirms a saved result. Failed previews are not saved. Use GET enhancement to observe progress, including after disconnecting.
An optional UUID operation_id makes identical retries idempotent. Reusing it with different inputs or starting another operation while one runs returns 409. A concurrent note edit prevents the final save and produces a failed operation with error code 409; read the note again before retrying. See CLI flags and MCP operations.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Team ID is an alphanumerical string that identifies a Team. This is externally referred to as a "Workspace".
Note ID is a numerical string that identifies a Note.
Body
Instructions or an explicit template, with optional retry and concurrency guards.
At least one of non-empty instructions or an explicit note_template_id is required. Existing template-only clients may continue using ApplyNoteTemplateRequest unchanged.
Instructions to revise current enhanced HTML, or to apply while regenerating with an explicit template.
102400Explicit template to regenerate from raw user notes and transcript. Omit to revise current enhanced HTML.
Target for an instruction-only revision. Omit to use the entry matching the note's last_note_template_id. An explicit template selects its own entry.
Optional client-generated UUID for idempotent retries. The server generates an ID when omitted.
Revision from the latest GetNote response. A stale value is rejected with 409; omission captures the current note revision.
x >= 0Response
Terminal enhancement snapshot; completed results have been durably saved.