Note Data Model

A Note is the top-level container for a single recording session. Its content is exposed through three kinds of children: Paragraphs (the transcript), NoteSummary (a one-page recap), and NoteDocument (a structured multi-section report). This page maps the entities and tells you which API to call for what.

​

Entity relationships

​

Entities

​

Note

The container created when a recording session starts (or when audio/text is imported). Identified by its guid field; API paths refer to it as {noteGuid}. Holds metadata such as title, source type, recording duration, and collaborators. Its actual content lives in the children below.

​

Paragraph

A semantic unit of a Note’s transcript — typically a speaker turn or topic chunk, not a prose paragraph. Each Paragraph carries transcript, translated (when translation was requested), summary (a short paragraph-level summary), and timestamps. Each text field is a TextObject of shape { type, content } (type is text/plain or text/markdown), and these fields become non-null in stages as transcription, translation, and summarization complete asynchronously.

​

NoteSummary

A single block of summary text covering the entire Note — what users call the “one-page” summary. Its content field is a TextObject ({ type, content }), not a raw string. A Note can have multiple NoteSummaries (different languages or templates). Unlike NoteDocument, it is not divided into sections.

​

NoteDocument

A structured multi-section document — for example, meeting minutes, action items, or sales call notes. Generated from a NoteDocumentTemplate that defines what sections exist. Each section is rendered separately. Use this when you need a templated, structured artifact rather than a free-form summary.

​

NoteDocumentTemplate

Defines the section structure for NoteDocuments. Either platform-managed (isManaged: true, e.g., “Meeting Minutes”) or team-custom. Browse available templates before creating a NoteDocument so you can pick the right shape.

​

Folder

Organizes Notes hierarchically. A Note belongs to at most one Folder. Folders can be user-owned or team-owned, with sharing rules.

​

What API should I call?

​

FAQ

Where is the “one-page” summary? It lives in NoteSummary. Call GET /v1/external/notes/{noteGuid}/summaries. NoteDocument is for multi-section structured reports — not single-page recaps. NoteSummary or NoteDocument — which should I use?

• Single block of summary text → NoteSummary.
• Multi-section structured report (driven by a template) → NoteDocument.

A Note can have both. Pick based on the shape your application expects. For a feature-by-feature comparison (available templates, creation paths, webhook support), see Summary And Document.