Skip to main content
GET
Get Note Document

Authorizations

Authorization
string
header
required

API key in format {id}.{secret}.

The notes an endpoint returns depend on the key type. A user key reaches the notes that user can see in the app, including notes in their own private folders. A system key (workspace or organization, no user identity) reaches only notes that sit in a folder shared with all workspace members. Notes in a private folder, in a folder shared with only some members, or in no folder at all fall outside a system key's read scope, and scopes do not widen that boundary.

List and search endpoints drop out-of-scope notes from the response without an error. Single-note reads and their sub-resources return 404, the same response as a deleted note. See What notes a system key reads.

Path Parameters

noteGuid
string
required

Note GUID

documentId
integer<int64>
required

Document ID

Query Parameters

format
enum<string>
default:text/markdown

Response format

Available options:
text/plain,
text/markdown

Response

Document details

A structured multi-section document (e.g., meeting minutes, action items) generated from a NoteDocumentTemplate. Unlike NoteSummary, it is divided into predefined sections. See Data Model.

id
integer<int64>
required

Document ID

Example:

456

noteGuid
string
required

The GUID of the note this document belongs to

Example:

"note-abc123-def456"

note
object
required

Note reference with minimal information

template
object
required

Summary information of a note document template

locale
enum<string>
required

Supported language locale

Available options:
ko_KR,
en_US,
de_DE,
ja_JP,
es_ES,
fr_FR,
id_ID,
vi_VN,
tr_TR,
uk_UA,
ru_RU,
hi_IN,
it_IT,
zh_CN,
ms_MY,
th_TH,
sv_SE
Example:

"ko_KR"

sections
object[]
required

Array of document sections

createdAt
string<date-time>
required

Document creation timestamp

Example:

"2025-10-20T12:35:26Z"

updatedAt
string<date-time>
required

Document last update timestamp

Example:

"2025-10-20T13:45:30Z"

truncated
boolean
default:false

true when the document was emitted as part of a deep-search response and its combined section text exceeded the search budget (5,000 chars). Plain document fetches always emit false.