> ## Documentation Index > Fetch the complete documentation index at: https://docs.tiro.ooo/llms.txt > Use this file to discover all available pages before exploring further. # Get Note Document > Retrieve a specific note document by ID. See [Template Based Documents](/template-based-documents/summary-and-document) for more details. ## OpenAPI ````yaml /openapi.yaml get /v1/external/notes/{noteGuid}/documents/{documentId} openapi: 3.1.0 info: title: Tiro API description: AI-powered note-taking and voice file processing API version: 1.0.0 contact: name: Tiro Support email: support@tiro.ooo url: https://tiro.ooo servers: - url: https://api.tiro.ooo description: Production server security: - BearerAuth: [] tags: - name: Note description: Operations for managing notes and their paragraphs - name: Note Share Link description: Manage share links for notes - name: Note Summary description: Operations for retrieving note summaries - name: Note Document description: Template-based document generation from notes - name: Note Document Template description: Operations for managing note document templates - name: Folder description: Operations for retrieving folders - name: Voice File description: Operations for voice file processing - name: Word Memory description: > Manage word memories to improve voice transcription accuracy. Register important terms like company names, people's names, and product names so Tiro recognizes them precisely during recording. Personal word memories (User) and a workspace's shared word memories (Workspace) are managed separately. The legacy team word memory endpoints (`/v1/external/teams/me/word-memories`) are deprecated — removed on 2026-06-30 — in favor of the workspace-explicit `/v1/external/workspaces/{workspaceGuid}/word-memories`. - name: Wiki description: | Access workspace wikis — unified knowledge graphs built from notes. Requires a workspace with wiki plan and activation enabled. - name: Organization description: > Endpoints for organization API keys. An organization key is issued by an organization admin, carries fixed scopes chosen at issuance, and can reach the notes in every workspace that belongs to the organization. Built for server-to-server integrations such as CRM sync — receive `note.ended` webhook events, generate documents for notes, and reconcile with the organization notes list. - name: Organization Management description: Operations for the authenticated user's organization. paths: /v1/external/notes/{noteGuid}/documents/{documentId}: get: tags: - Note Document summary: Get Note Document description: > Retrieve a specific note document by ID. See [Template Based Documents](/template-based-documents/summary-and-document) for more details. operationId: getNoteDocument parameters: - name: noteGuid in: path description: Note GUID required: true schema: type: string example: abc123xyz - name: documentId in: path description: Document ID required: true schema: type: integer format: int64 example: 456 - name: format in: query description: Response format required: false schema: type: string enum: - text/plain - text/markdown default: text/markdown responses: '200': description: Document details content: application/json: schema: $ref: '#/components/schemas/NoteDocument' example: id: 456 noteGuid: note-abc123-def456 note: guid: note-abc123-def456 webUrl: https://tiro.ooo/n/xQ8YKnZUPGHNB template: id: 1 title: 영업 보고서 locale: ko_KR sections: - content: type: text/plain content: 회의는 신제품 출시 계획에 대해 논의했습니다... createdAt: '2025-10-20T12:35:26Z' - content: type: text/plain content: |- - 다음 주까지 견적서 발송 - 담당자 배정 createdAt: '2025-10-20T12:35:26Z' createdAt: '2025-10-20T12:35:26Z' updatedAt: '2025-10-20T13:45:30Z' text/markdown: schema: type: string example: | # 영업 보고서 회의는 신제품 출시 계획에 대해 논의했습니다... ## 액션 아이템 - 다음 주까지 견적서 발송 - 담당자 배정 '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Document not found content: application/json: schema: $ref: '#/components/schemas/Error' components: schemas: NoteDocument: type: object description: > 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](/fundamentals/note-data-model). required: - id - noteGuid - note - template - locale - sections - createdAt - updatedAt properties: id: type: integer format: int64 description: Document ID example: 456 noteGuid: type: string description: The GUID of the note this document belongs to example: note-abc123-def456 note: $ref: '#/components/schemas/NoteRef' template: $ref: '#/components/schemas/NoteDocumentTemplateSummary' locale: $ref: '#/components/schemas/SupportedLocale' sections: type: array description: Array of document sections items: $ref: '#/components/schemas/NoteDocumentSection' createdAt: type: string format: date-time description: Document creation timestamp example: '2025-10-20T12:35:26Z' updatedAt: type: string format: date-time description: Document last update timestamp example: '2025-10-20T13:45:30Z' truncated: type: boolean default: false description: | `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`. Error: type: object required: - error properties: error: type: object required: - code - errorType - message properties: code: type: integer description: > 6-digit error code in `AAABBB` form: first 3 digits match the HTTP status, last 3 digits are a per-status serial (e.g. `404018`). Use only when you need to distinguish specific error cases within the same HTTP status — values may be added or renumbered across releases. For general client branching, prefer `errorType`. example: 404018 errorType: type: string description: > Stable, coarse-grained error category. Recommended default for client-side branching: the value-to-status mapping is part of the API contract and will not change without a breaking-change notice. Typical use: - `unauthorized` → trigger re-authentication - `forbidden` → surface a permission error to the user - `not_found` → treat as missing resource - `too_many_requests` → back off and retry - `internal_error` → retry with exponential backoff enum: - bad_request - unauthorized - forbidden - not_found - not_acceptable - conflict - payload_too_large - unprocessable_entity - too_many_requests - internal_error example: not_found message: type: string description: >- Human-readable error message. Not stable; do not use for branching. example: 'No team found for user #217' detail: type: string nullable: true description: Additional error details example: null NoteRef: type: object description: Note reference with minimal information required: - guid - webUrl properties: guid: type: string description: Note GUID example: note-abc123-def456 webUrl: type: string format: uri description: Web URL to access the note example: https://tiro.ooo/n/xQ8YKnZUPGHNB NoteDocumentTemplateSummary: type: object description: Summary information of a note document template required: - id - title properties: id: type: integer format: int64 description: Template ID example: 1 title: type: string description: Template title example: 영업 보고서 SupportedLocale: type: string enum: - 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 description: Supported language locale example: ko_KR NoteDocumentSection: type: object description: A section within a note document required: - content - createdAt properties: content: allOf: - $ref: '#/components/schemas/TextObject' - description: Generated section content createdAt: type: string format: date-time description: Section creation timestamp example: '2025-10-20T12:35:26Z' TextObject: type: object required: - type - content properties: type: type: string enum: - text/plain - text/markdown description: MIME type of the text content example: text/plain content: type: string description: The actual text content example: Hello everyone, welcome to today's meeting... securitySchemes: BearerAuth: type: http scheme: bearer description: API key in format {id}.{secret} ````