Glossary - Tiro Docs

This page lists concepts that the Tiro app and the API call by different names.

Check the different names first

The screen label and the API name diverge most here.

Name in the app	Name in the API	Same concept
One-Pager	`summary`	The AI-generated note summary. `GET /v1/external/notes/{noteGuid}/summaries` returns only metadata for a list of summaries; take the `id` value from each list item and pass it as the `{summaryId}` path parameter to call `GET /v1/external/notes/{noteGuid}/summaries/{summaryId}` for the actual content.

Searching the API for “One-Pager” turns up nothing. In the API it’s called summary. List summaries with GET /v1/external/notes/{noteGuid}/summaries, then take the id of the item you want and pass it as {summaryId} in GET /v1/external/notes/{noteGuid}/summaries/{summaryId}.

Full term mapping

Name in the app	Name in the API	Notes
Note	`note` (identified by `noteGuid`)	Same in the app and the API
One-Pager	`summary`	Different name (see above)
Transcript	`transcript` · `paragraphs`	Same name in the app and the API. The spoken record is `transcript`; the paragraph-level breakdown is `paragraphs`.
Document	`document`	A document created from a template
Template	`documentTemplate`
Folder	`folder`	Same in the app and the API. The internal implementation name differs (see below).
Share	`shareLink`
Word Memory	`wordMemory`
Wiki	`wiki` · `wikiPage`
Voice file	`voiceFile`	An uploaded audio or video file
Workspace	`workspace` (`workspaceGuid`)	Some responses still carry legacy “team” wording such as `isTeamFolder`

Both the app and the API call a folder folder. Inside Tiro’s implementation, though, it’s called thread, so you may see traces of that in some legacy fields (for example, legacyThreadId). In new code, use only the folder fields.