Summary And Document

​

Overview

Tiro has NoteDocument and NoteSummary. They differ in purpose and in how they are created. For the full Note structure, see Note Data Model.

​

NoteDocument vs NoteSummary

​

NoteDocument

NoteDocument is a document divided into sections. You can create and retrieve it through the API. Key characteristics:

• Created using templates with defined sections
• Supports custom templates with user instructions
• Only create and read (list/single) are available via API. Update and delete are not yet available via API.
• Webhook events for real-time notifications

Example templates:

• 회의록 (Meeting Minutes)
• Custom templates you create

API endpoints:

• POST /v1/external/notes/{noteGuid}/documents - Generate document
• GET /v1/external/notes/{noteGuid}/documents - List documents
• GET /v1/external/notes/{noteGuid}/documents/{documentId} - Get document

​

NoteSummary

NoteSummary provides quick-format templates for different presentation styles. Key characteristics:

• Optimized for specific use cases (pitches, one-pagers, etc.)
• Full API support for retrieving summaries
• Webhook events for real-time notifications
• Currently created through Tiro app interface only

Example templates:

• One-Pager
• Pitch
• And other format-specific templates

API endpoints:

• GET /v1/external/notes/{noteGuid}/summaries - List summaries
• GET /v1/external/notes/{noteGuid}/summaries/{summaryId} - Get summary with content

Webhook events:

• note_summary.generated - Summary creation complete
• note_summary.updated - Summary modified
• note_summary.deleted - Summary deleted