Home/Glossary

Meeting bot glossary

Short, clear definitions for the terms you meet when you build on meeting bot infrastructure.

Each entry links to a fuller page with examples and API context.

Meeting botJoins and capturesMeeting bot APIYou drive it from codeAI notetakerSummaries and actionsMeetingintelligenceThe wider categoryMeeting botJoins and capturesMeeting bot APIYou drive it from codeAI notetakerSummaries and actionsMeeting intelligenceThe wider category
Each layer sits on the one before it.
Zoom access

Getting into a Zoom call

Zoom's three access terms, and when each one applies.

TermWhat it isWhen it appliesZoom RTMSZoom's own media streamYour own tenant, no botZoom OBFA consented per-user connectionMeetings outside your accountZoom ZAKA per-user token you fetchMeetings on your own accountZoom RTMSWhat it is: Zoom's own media streamWhen it applies: Your own tenant, no botZoom OBFWhat it is: A consented per-user connectionWhen it applies: Meetings outside youraccountZoom ZAKWhat it is: A per-user token you fetchWhen it applies: Meetings on your ownaccount
Which one applies depends on whose meeting it is.
FAQ

Frequently asked questions

What is Zoom RTMS (Realtime Media Streams)?

Zoom RTMS gives your app live access to a meeting's audio, video and transcript over a WebSocket. That includes per-participant streams.

It is Zoom's own approach, so you subscribe to the media Zoom sends instead of using a client bot.

It covers Zoom only. If you also need Google Meet and Microsoft Teams, you can run RTMS next to separate integrations.

Or you can use a bot-based API like MeetStream, which sends your own bot into all three platforms behind one interface.

What is speaker diarization and why does a meeting API need it?

Speaker diarization answers who spoke when.

It splits an audio stream into turns and tags each turn with a speaker, so the transcript reads as a conversation rather than one block of text.

Diarization infers the split from a single track, and per-participant audio removes the guesswork.

Each speaker arrives on their own stream, keyed by participant ID, so the labels are exact from the start.

What is per-participant audio and how is it different from a mixed recording?

A mixed recording blends every speaker into one track.

Per-participant audio gives you each person on a separate stream, tagged with their participant ID.

That split lets you run transcription, sentiment or coaching logic on one speaker with no bleed from the others.

You also get the right labels without diarization.

MeetStream sends these streams over WebSocket in real time at roughly 200ms on Zoom, Google Meet and Teams.

What is a meeting webhook and how does it work?

A meeting webhook is an HTTP callback.

It pushes an event to your endpoint the moment something happens, so your app learns that a bot joined or a recording finished without polling.

You register a URL, and the service sends a short payload for each step: joining, recording, transcript ready, and the bot leaving.

With MeetStream you point webhooks at your own endpoint.

You then get participant events and status changes in real time, so you can drive things like CRM updates with no polling loop.

From definitions to production

Every term here ships in one API. Join, record, stream and transcribe meetings from your own code.