Overview
Tiro provides two types of template-based document generation features: NoteDocument and NoteSummary. These are separate systems with different purposes and API support.
NoteDocument vs NoteSummary
| Feature | NoteDocument | NoteSummary |
|---|---|---|
| Purpose | Structured meeting documents | Quick format templates |
| Templates | 회의록 (Meeting Minutes), Custom templates | One-Pager, Pitch, etc. |
| API Support | ✅ Full support | 🚧 Coming soon |
| Webhook Support | ✅ note_document.* events | 🚧 Coming soon |
| Created via | API or Tiro app | Tiro app only |
NoteDocument
NoteDocument is designed for structured, section-based documents that you can create, retrieve, and manage via the API. Key characteristics:- Created using templates with defined sections
- Supports custom templates with user instructions
- Full API CRUD operations available
- Webhook events for real-time notifications
- 회의록 (Meeting Minutes)
- Custom templates you create
POST /v1/external/notes/{noteGuid}/documents- Generate documentGET /v1/external/notes/{noteGuid}/documents- List documentsGET /v1/external/notes/{noteGuid}/documents/{documentId}- Get document
NoteSummary
NoteSummary provides quick-format templates for different presentation styles. Currently, these can only be created through the Tiro app. Key characteristics:- Optimized for specific use cases (pitches, one-pagers, etc.)
- Created through Tiro app interface
- 🚧 API support coming soon
- 🚧 Webhook support coming soon
- One-Pager
- Pitch
- And other format-specific templates
API Support Status
Currently Supported
NoteDocument API
Create and retrieve structured documents via API
NoteDocument Webhooks
Real-time notifications for document events
Coming Soon
NoteSummary API & Webhook SupportFull API and webhook support for NoteSummary is coming soon:
- Webhook events:
note_summary.created,note_summary.updated, etc. - API endpoints: Create, retrieve, and manage NoteSummary documents

