Skip to main content
PATCH
Update an AI enhanced note
Only the note owner can update an enhanced entry. Read the note first and send its revision as expected_revision to protect concurrent edits. A stale revision returns 409; omitting the field preserves compatibility with existing clients. After a successful update, fetch the note again for its new whole-note revision before saving another edit. The response contains the saved enhanced entry, not the new note revision. See agent enhancement for revisions using instructions.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

team_id
string
required

Team ID is an alphanumerical string that identifies a Team. This is externally referred to as a "Workspace".

note_id
string
required

Note ID is a numerical string that identifies a Note.

enhanced_note_id
string
required

Enhanced Note ID

Body

application/json

Enhanced Note fields that need to be updated. All omitted fields are left unmodified.

expected_revision
integer<int64> | null

Whole-note revision from the latest GetNote response. A stale value is rejected with 409; omission preserves compatibility with existing clients.

Required range: x >= 0
title
string | null
Example:

"Team Note"

content
string | null
Maximum string length: 102400

Response

updated enhanced note response

ai_note
object