Participants & Speaker Timeline
Participants & Speaker Timeline
Who was in the meeting, and who spoke when
Two endpoints turn a recording into attributable data: get_participants (who was there) and get_speaker_timeline (who spoke when, down to byte ranges of the audio file).
List participants
Each participant entry carries:
Identify participants uniquely
Display names collide (“John” twice) and change mid-meeting. Use the IDs instead:
deviceIdis unique per participant per meeting and consistent acrossget_participants, the speaker timeline (speakerId), and live audio frames (speaker_id).streamIdslink a participant to their per-participant audio/video files.- Speaker labels in transcripts carry per-word
speakerattribution you can map back by name.
The speaker timeline
The response is a list of chunks, each mapping a slice of the recorded audio to a speaker:
Because chunks reference byte ranges of the audio file at a known sample rate, 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.
Use cases this unlocks
- Talk-time ratios for sales coaching (rep vs prospect seconds, straight from chunk math)
- 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
CLI: meetstream bot participants <id> and meetstream bot timeline <id>.
