> ## 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 Summary > Retrieve a specific summary with full content. - Default format: Markdown (`text/markdown`) - Use the `format` query parameter to request `text/plain` instead See [Template Based Documents](/template-based-documents/summary-and-document) for more details. ## OpenAPI ````yaml /openapi.yaml get /v1/external/notes/{noteGuid}/summaries/{summaryId} 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}/summaries/{summaryId}: get: tags: - Note Summary summary: Get Note Summary description: > Retrieve a specific summary with full content. - Default format: Markdown (`text/markdown`) - Use the `format` query parameter to request `text/plain` instead See [Template Based Documents](/template-based-documents/summary-and-document) for more details. operationId: getNoteSummary parameters: - name: noteGuid in: path description: Note GUID required: true schema: type: string example: abc123xyz - name: summaryId in: path description: Summary ID from list endpoint required: true schema: type: integer format: int64 example: 123 - name: format in: query description: Content format required: false schema: type: string enum: - text/markdown - text/plain default: text/markdown example: text/markdown responses: '200': description: Summary with full content content: application/json: schema: $ref: '#/components/schemas/NoteSummary' example: id: 123 noteGuid: note-abc123-def456 note: guid: note-abc123-def456 webUrl: https://tiro.ooo/n/xQ8YKnZUPGHNB template: id: 1 title: One-Pager locale: ko_KR content: type: text/markdown content: |- # Meeting Summary ## Key Points - Discussed Q4 roadmap - Budget approved... createdAt: '2025-12-12T12:00:00Z' updatedAt: '2025-12-12T12:00:00Z' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Note or summary not found content: application/json: schema: $ref: '#/components/schemas/Error' components: schemas: NoteSummary: type: object description: > A single block of summary text for a Note (the "one-page" summary). A Note can have multiple NoteSummaries in different languages or templates. Unlike NoteDocument, it is not divided into sections. See [Data Model](/fundamentals/note-data-model). required: - id - noteGuid - note - locale - content - createdAt - updatedAt properties: id: type: integer format: int64 description: Summary ID example: 123 noteGuid: type: string description: Associated note GUID example: note-abc123-def456 note: $ref: '#/components/schemas/NoteRef' template: nullable: true allOf: - $ref: '#/components/schemas/NoteSummaryTemplate' description: >- Template used for this summary. Null if the template has been deleted. locale: $ref: '#/components/schemas/SupportedLocale' content: $ref: '#/components/schemas/TextObject' createdAt: type: string format: date-time description: Creation timestamp example: '2025-12-12T12:00:00Z' updatedAt: type: string format: date-time description: Last update timestamp example: '2025-12-12T12:05:00Z' 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 NoteSummaryTemplate: type: object description: Summary template information required: - id - title properties: id: type: integer format: int64 description: Template ID example: 1 title: type: string description: Template title (e.g., One-Pager, Pitch) example: One-Pager 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 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} ````