Skip to main content

Overview

Tiro provides two types of template-based document generation features: NoteDocument and NoteSummary. These are separate systems with different purposes and API support. Template-based document types in Tiro

NoteDocument vs NoteSummary

FeatureNoteDocumentNoteSummary
PurposeStructured meeting documentsQuick format templates
Templates회의록 (Meeting Minutes), Custom templatesOne-Pager, Pitch, etc.
API Support✅ Full support🚧 Coming soon
Webhook Supportnote_document.* events🚧 Coming soon
Created viaAPI or Tiro appTiro 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
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. Currently, these can only be created through the Tiro app.
Coming Soon: API and webhook support for NoteSummary is actively being developed and will be available soon.
Key characteristics:
  • Optimized for specific use cases (pitches, one-pagers, etc.)
  • Created through Tiro app interface
  • 🚧 API support coming soon
  • 🚧 Webhook support coming soon
Example templates:
  • One-Pager
  • Pitch
  • And other format-specific templates

API Support Status

Currently Supported

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
Stay tuned for updates in our Changelog.