> ## 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. # List Organization Note Document Templates > List the org-owned note document templates of the organization bound to the API key, with cursor-based pagination. Requires an organization API key; personal, workspace, and legacy team keys return `401`. ## OpenAPI ````yaml /openapi.yaml get /v1/external/organizations/me/note-document-templates 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/organizations/me/note-document-templates: get: tags: - Note Document Template summary: List Organization Note Document Templates description: > List the org-owned note document templates of the organization bound to the API key, with cursor-based pagination. Requires an organization API key; personal, workspace, and legacy team keys return `401`. operationId: listOrganizationNoteDocumentTemplates parameters: - name: cursor in: query description: Cursor for the next page required: false schema: type: string - name: size in: query description: Page size (default 100, max 200) required: false schema: type: integer default: 100 minimum: 1 maximum: 200 responses: '200': description: Paginated list of the organization's note document templates content: application/json: schema: allOf: - $ref: '#/components/schemas/PageCursorResponse' - type: object properties: content: type: array items: $ref: '#/components/schemas/NoteDocumentTemplate' examples: success: summary: Organization templates list value: content: - id: 51 title: 회의록 description: 회의 내용을 체계적으로 정리하는 템플릿 sections: - id: 61 title: 주요 논의 사항 sectionType: PLAIN_TEXT userInstruction: 회의에서 논의된 핵심 주제를 요약해주세요 favorite: false isManaged: false isEditable: true createdAt: '2025-10-20T12:35:26Z' nextCursor: cursor_string empty: summary: Empty templates list value: content: [] nextCursor: null '401': description: Unauthorized — missing key, invalid key, or not an organization key content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: Forbidden — the organization key cannot access these templates content: application/json: schema: $ref: '#/components/schemas/Error' components: schemas: PageCursorResponse: type: object required: - content - nextCursor properties: content: type: array items: {} description: Array of items for current page nextCursor: type: string nullable: true description: Cursor for next page, null if last page example: opaque-cursor-string NoteDocumentTemplate: type: object description: | A template that defines the section structure for NoteDocuments. Either platform-managed (`isManaged: true`) or team-custom. Use this to pick or design the shape of a generated document. See [Data Model](/fundamentals/note-data-model). required: - id - title - description - sections - favorite - isManaged - isEditable - createdAt properties: id: type: integer format: int64 description: Template ID example: 1 title: type: string description: Template title example: 회의록 description: type: string description: Template description example: 회의 내용을 체계적으로 정리하는 템플릿 sections: type: array description: Template sections items: $ref: '#/components/schemas/NoteDocumentTemplateSection' favorite: type: boolean description: Whether the template is favorited by the user default: false example: false isManaged: type: boolean description: Whether the template is managed by the system example: true isEditable: type: boolean description: Whether the template is editable example: false createdAt: type: string format: date-time description: Template creation timestamp example: '2025-10-20T12:35:26Z' lastUsedAt: type: string format: date-time nullable: true description: Timestamp when the template was last used. Null if never used. example: '2025-10-20T14:20:15Z' 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 NoteDocumentTemplateSection: type: object description: Section within a document template required: - id - title - sectionType - userInstruction properties: id: type: integer format: int64 description: Section ID example: 1 title: type: string description: Section title example: 주요 논의 사항 sectionType: $ref: '#/components/schemas/NoteDocumentTemplateSectionType' userInstruction: type: string description: User-provided instruction for this section example: 회의에서 논의된 핵심 주제를 요약해주세요 NoteDocumentTemplateSectionType: type: string description: Type of document template section enum: - PLAIN_TEXT - ACTION_ITEMS - INFORMATIONAL_QNA - EXAMPLE example: PLAIN_TEXT securitySchemes: BearerAuth: type: http scheme: bearer description: API key in format {id}.{secret} ````