Unified Speaker Timeline
GET /api/v1/bots/{bot_id}/get_speaker_timeline returns who spoke and when in a meeting. The timeline is available after the bot leaves the meeting. Until then, the endpoint returns 404 with Manifest file not found. It may still be processing.
By default, each platform returns its own timeline format (Google Meet chunks, Zoom sessions, Microsoft Teams slices), as described in the API reference for this endpoint. To get the same format for every platform, add format=unified.
One format for every platform (format=unified)
With format=unified, Google Meet, Microsoft Teams and Zoom bots all return the same shape, so you need only one parser. Without format, responses are unchanged, so existing integrations keep working.
- The value is not case-sensitive:
unifiedandUNIFIEDboth work. - An empty value (
format=) gives the default response. - Any other value returns
400withUnsupported format. Supported values: unified.
Example response
Top-level fields
Chunk fields
Every chunk always has every field below. A value a platform can’t provide is null; no field is ever left out.
To get seconds from the start of the audio, divide timestamp (or endTimestamp) by 1,000,000.
Platform differences
For some older Zoom recordings the start of the audio is not known. Then timestamp, endTimestamp, startByte and endByte are null, and startTime / endTime still give the wall-clock times.
Parsing example
The same code works for every platform:
Current limitation
For bots whose meeting data is stored in a data-residency region outside the US, format=unified returns 409 for now. Call without format to get their timeline in the platform’s own format.
Large timelines
Most timelines are returned inline: the response body is the timeline JSON itself.
Long or busy meetings can produce timelines too large to return in one API response (about 5 MB or more). For those, the endpoint still returns 200 OK, but the body is a small object with a download link instead of the timeline:
The unified format can be smaller or larger than a platform’s own format, so the same meeting may come back inline in one format and as a download link in the other. Always check for speaker_timeline_url.
Handling both shapes
Check for speaker_timeline_url and download the timeline when it is present:
The download link does not need your API key. Treat it like the meeting data itself and do not share it.
