Participants & Speaker Timeline
Two endpoints turn a recording into attributable data: get_participants (who was there) and get_speaker_timeline (who spoke when).
Platform support
See the capability matrix for everything else each platform supports.
List participants
Each participant entry carries:
Depending on the platform, entries can also carry isHost and first-seen and last-updated timestamps.
The file is written as the meeting goes. 404 (Participants file not found for this bot) means the bot never got into the meeting or the file is not uploaded yet.
After post-call processing, observed participants may also have a calendar_email matched from an invite on your connected calendar. It is separate from the platform’s email field. See Calendar Emails on Participants for where it appears, which event is used, and how names are matched.
Identify participants uniquely
Display names collide (“John” twice) and change mid-meeting. Use the IDs instead:
deviceIdis unique per participant per meeting. It matchesparticipant.extra_data.<platform>.static_participant_idin the per-participant audio and per-participant video responses. On Google Meet it is also thespeakerIdin the speaker timeline and thespeaker_idin live audio frames.- On Zoom, the number in
zoom_user_<id>is the Zoom user ID used in the Zoom speaker timeline (user_id) and in live audio frames. - On Teams, the speaker timeline’s
speaker_ididentifies the speaker; match onspeaker(the display name) when you join it to other data. - Speaker labels in transcripts carry per-word
speakerattribution you can map back by name.
The speaker timeline
Available after the bot leaves. 404 (Manifest file not found. It may still be processing.) means it is not ready yet.
Google Meet
Zoom
Microsoft Teams
A list of chunks, each mapping a slice of the recorded audio to a speaker:
Chunks reference byte ranges of the mixed audio file at a known sample rate, so you can compute exact timestamps (seconds = startByte / 2 / sampleRate for PCM16 mono), cut per-speaker clips, or build talk-time analytics without running diarization yourself.
While recording is paused, no speaking turns are recorded on Zoom.
Use cases this unlocks
- Talk-time ratios for sales coaching (rep vs prospect seconds, straight from the timeline)
- Speaker-accurate clip extraction (“play me everything the customer said”)
- Cross-referencing: join timeline speakers to transcript words to per-participant files via the shared IDs
For live join and leave events during the call, use the participant_events.join and participant_events.leave webhooks in webhooks and events. For why a bot never got into the meeting, see bot status and error codes.
CLI: meetstream bot participants <id> and meetstream bot timeline <id>.
