Glossary - Tiro Docs

The name you see in the Tiro app and the field name in an API response aren’t always the same. Start with the concepts whose names differ, and you’ll find the data you want in a response much faster.

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. Fetch it with `include: ["summary"]` when you get a note.

Searching the API for “One-Pager” turns up nothing. In the API it’s called summary, so request it with include: ["summary"].

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.

​Check the different names first

​Full term mapping

Check the different names first

Full term mapping