Skip to navigation

Participants & Speaker Timeline

Who was in the meeting, and who spoke when
View as Markdown

Two endpoints turn a recording into attributable data: get_participants (who was there) and get_speaker_timeline (who spoke when).

Platform support

ZoomGoogle MeetMicrosoft Teams
Participant list (get_participants)YesYesYes
Participant ID (deviceId) looks likezoom_user_16778240spaces/AbCdEf/devices/185The participant’s Teams identifier
Live join and leave eventsparticipant_events.join / .leaveSameSame
Host flagThe meeting hostThe meeting hostThe meeting organizer
Speaker timeline formatSpeaking turns with start and end times (sessions)Byte ranges of the audio (chunks)Short slices of the audio (about 1 s each), each labeled with the speaker
How the active speaker is detectedZoom’s per-speaker audioAudio levels of each participant’s trackTeams’ speaker identifiers on the mixed audio; overlapping speech goes to one speaker

See the capability matrix for everything else each platform supports.

List participants

curl "https://api.meetstream.ai/api/v1/bots/<BOT_ID>/get_participants" \
-H "Authorization: Token <YOUR_API_KEY>"

Each participant entry carries:

FieldWhat it is
deviceIdThe platform’s identifier for this participant in this meeting (shapes in the table above). Your key for joining data across endpoints
displayName / fullNameNames as shown in the meeting. Zoom entries carry fullName only
profilePictureAvatar URL when the platform exposes one (null on Zoom)
status / humanized_statusLast known state: in_meeting or not_in_meeting
streamIdsThe participant’s media stream IDs

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:

  • deviceId is unique per participant per meeting. It matches participant.extra_data.<platform>.static_participant_id in the per-participant audio and per-participant video responses. On Google Meet it is also the speakerId in the speaker timeline and the speaker_id in 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_id identifies the speaker; match on speaker (the display name) when you join it to other data.
  • Speaker labels in transcripts carry per-word speaker attribution you can map back by name.

The speaker timeline

curl "https://api.meetstream.ai/api/v1/bots/<BOT_ID>/get_speaker_timeline" \
-H "Authorization: Token <YOUR_API_KEY>"

Available after the bot leaves. 404 (Manifest file not found. It may still be processing.) means it is not ready yet.

A list of chunks, each mapping a slice of the recorded audio to a speaker:

{
"chunks": [
{ "chunkIndex": 0, "timestamp": "115360815932", "sampleRate": 48000,
"speakerId": "spaces/AbCdEf/devices/242", "speakerName": "Jane Smith",
"startByte": 0, "endByte": 98300 }
],
"lastUpdated": "2026-09-20T04:54:51.493Z"
}

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>.