Get Note Document
Retrieve a specific note document by ID.
See Template Based Documents for more details.
인증
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.
쿼리 매개변수
Response format
text/plain, text/markdown 응답
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.
Document ID
456
The GUID of the note this document belongs to
"note-abc123-def456"
Note reference with minimal information
Summary information of a note document template
Supported language locale
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 "ko_KR"
Array of document sections
Document creation timestamp
"2025-10-20T12:35:26Z"
Document last update timestamp
"2025-10-20T13:45:30Z"
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.