# Meeting Bot API for Zoom, Google Meet & Teams

> Meeting bot API for Zoom, Google Meet and Microsoft Teams: real-time audio, per-participant video and transcripts from $0.35/hr.

Source: https://meetstream.ai/meeting-bot-api

## Meeting Bot API for Zoom, Google Meet, and Microsoft Teams

One API sends a bot into a Zoom, Google Meet or Microsoft Teams call and returns the recording, a separate audio and video stream for every participant, and a transcript. No SDK per platform, no infrastructure of your own, from $0.35 per bot-hour.

### What is a meeting bot API?

A meeting bot API puts a participant into a video call from your code and hands the media back to your application. Instead of asking a user to record their own call and upload a file, you make one request, a bot joins the meeting, and the recording, per-participant streams and transcript arrive at a webhook when the call ends.

The alternative is to build against each platform separately. That means three different auth models, three sets of plan requirements, and in Microsoft's case a specific language and operating system. It also means your product only works when your customer holds the right licence, which is rarely true in practice. A bot behaves the same way on every platform and on accounts you do not control.

### Send a bot into any meeting with one request

The same call works for Zoom, Google Meet and Microsoft Teams. MeetStream reads the platform from the link.

```
curl -X POST https://api.meetstream.ai/api/v1/bots/create_bot \ -H "Authorization: Token $MEETSTREAM_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "meeting_link": "https://zoom.us/j/74648392", "bot_name": "Acme Notetaker", "transcription": { "provider": "meetstream" }, "webhook_url": "https://your-app.example.com/meetstream" }'
```

When the meeting ends you get the composed recording, a separate audio and video URL for every participant, and the transcript.

```
{ "event": "bot.done", "bot_id": "bot_9fJ2p", "platform": "zoom", "recording": { "mp4_url": "https://media.meetstream.ai/..." }, "participants": [ { "name": "Amy Stace", "audio_url": "...", "video_url": "..." }, { "name": "Theo Flynn", "audio_url": "...", "video_url": "..." } ], "transcript_url": "https://api.meetstream.ai/api/v1/transcript/..." }
```

### What you get back from every meeting

- Composed MP4 in grid or speaker view. Full detail on the recording API page.

- Per-participant audio and video , one real stream per person on all three platforms.

- Transcripts with speaker labels, on our in-house engine or on Sarvam, Gemini, Deepgram, AssemblyAI or JigsawStack. See the transcription API .

- Real-time audio and video over a secure WebSocket at roughly 200ms, covered on the real-time transcripts page.

- Participant events for join, leave and admission, plus the meeting chat.

- Outbound actions : the bot can post a chat message, send an image, or speak in the room through voice agents .

- Calendar integration , so bots are scheduled from a connected calendar up to three months ahead rather than dispatched manually.

### Platform coverage

One integration covers all three. Each platform has its own rules about who may record, on which plan, and whether a bot is admitted at all, so each has a page of its own with the detail and the source links.

If you are choosing where to start, Zoom is the most permissive, Google Meet is the one most likely to deny the bot outright, and Teams is the one that most changes a build-versus-buy decision.

### What the platforms actually enforce

This is the part that breaks integrations in production, and it is worth reading before you scope the work. Every claim links to the platform's own documentation.

Three of those deserve a sentence, because they are the ones teams discover late.

Teams lobbies external bots by default. The ExternalBotAccessMode policy defaults to RequireApprovalWhenDetected , which overrides the meeting's own lobby setting. Teams also fingerprints bots on join .

Google Meet denies bots by name. When a host unchecks "Anyone can ask to join", Google documents that third-party bots, like note takers, are automatically denied with no action from the host.

Zoom requires OBF tokens since 2 March 2026. OBF is short for On Behalf Of. A user who authorized your app must already be in the meeting for the join to succeed. MeetStream handles the token; the constraint is worth knowing anyway.

None of this makes bots unworkable. It means admission is a state your product should handle rather than assume, and MeetStream sends participant events precisely so you can.

### Building it yourself

It is a reasonable thing to consider, so here is the honest shape of it.

Zoom is the most approachable. Realtime Media Streams went generally available in June 2025 and gives per-participant media with no bot in the room. If your users will install a Zoom Marketplace app, that is a genuinely good path and you may not need a vendor for Zoom at all.

Google Meet is the hardest to ship commercially. The Meet Media API is a developer preview that requires the Cloud project, the OAuth principal and every participant in the call to be enrolled in the preview programme, and Google's pre-GA terms bar giving access to users outside your own company. It also caps at three audio streams that rotate between the loudest speakers, so it cannot do per-participant capture.

Microsoft Teams is the most expensive. Microsoft states that an application-hosted media bot must be written in C# and run on Windows Server in Azure , that the C++ and Node.js APIs do not support real-time media at all, and that a video-enabled bot may sustain only one or two concurrent media sessions per CPU core. Concurrency becomes a fleet-sizing exercise before you have shipped a feature.

The summary most teams land on: build on Zoom RTMS if Zoom is all you need and your users will install your app, and use a bot API the moment you need Google Meet or Teams as well.

### Meeting bot API pricing

A bot costs $0.35 per bot-hour . Transcription adds $0.10 per hour, so a recorded and transcribed meeting is $0.45 per hour all-in , falling toward $0.25 per bot-hour at volume. Thirty days of storage is included rather than metered, and every account starts with $5 of free credit.

There is no seat licence, no platform fee and no minimum commitment, so the bill tracks usage rather than headcount. The pricing page has the full breakdown, and the Recall.ai comparison covers how it compares if you are switching.

### Limits and operational detail

Session length. Four hours by default, extendable to ten hours through the API.

Concurrency. No cap on simultaneous bots and no limit to request an increase to.

Joining. On-demand bots join in under ten seconds on average. Scheduled bots join on time and can be scheduled up to three months ahead.

Storage and regions. Thirty days by default, or your own S3 bucket so retention is yours from the first byte. United States by default, with EU, Australia, Japan and the Middle East available and other regions on request.

Security. ISO 27001 certified. SOC 2 Type 2 is under audit rather than complete. No HIPAA certification and no Business Associate Agreements today. The security page is kept current.

Service levels. Agreed per customer rather than published as one number.

### How we know this

MeetStream runs meeting bots on Zoom, Google Meet and Microsoft Teams for more than 30 products in production. The platform constraints on this page are the ones our own bots hit, not a summary of someone else's writing, and every one of them links to the vendor documentation so you can check it rather than trust us. Where we could not source a claim, we left it out.

We have also tried to be straight about where we are weaker. Zoom RTMS is a real alternative to a bot and we say so above. We are ISO 27001 certified but SOC 2 Type 2 is still under audit, and we do not hold a HIPAA certification or sign Business Associate Agreements today.

Platform rules change often. If something here no longer matches the vendor documentation, tell us and we will fix it. Written by Sidhdharth Sivasubramanian, co-founder and CEO of MeetStream. Last reviewed 26 August 2026.

### Frequently asked questions

A meeting bot API lets your application put a participant into a video call programmatically and get the media back. You send a meeting link, a bot joins under a name you choose, and you receive a recording, per-participant audio and video, and a transcript when the call ends.

Zoom, Google Meet and Microsoft Teams, through one integration. Each has its own page with the platform-specific rules: Zoom, Google Meet and Microsoft Teams.

No. That is the main reason to use a bot rather than a platform's native recording API. Zoom cloud recording requires a paid plan and Google Meet recording requires specific Workspace editions, but a bot records what it receives as a participant regardless of the host's plan.

Not automatically, and any vendor who says otherwise is overselling. Microsoft Teams sends external bots to the lobby by default, and Google Meet denies bots outright under some access settings. MeetStream sends participant events so your application knows whether the bot was admitted, denied or is still waiting.

Yes, on all three platforms. Speaker attribution comes from the platform's own participant separation rather than a diarization model guessing from a mixed track.

Bots created on demand join in under ten seconds on average. Scheduled bots join at the scheduled time. A bot can be scheduled up to three months in advance.

Four hours by default, extendable to ten hours through the API. There is no cap on how many bots run at the same time.

$0.35 per bot-hour for recording, $0.45 per hour with transcription, dropping toward $0.25 per bot-hour at volume. Thirty days of storage is included rather than metered, and every account starts with $5 of free credit.

Thirty days by default. Connect your own S3 bucket and everything is written into your account from the first byte, so your retention policy governs it. The default region is the United States, with EU, Australia, Japan and the Middle East available and other regions on request.

Yes. Real-time audio and video stream over a secure WebSocket at roughly 200ms, and the bot can post chat messages, send images, and speak in the meeting through the voice agents API.

Yes, by design. The bot appears in the participant list under a name you choose, and all three platforms show their own recording indicators, which on Zoom cannot be disabled for external participants on any plan.

MeetStream is ISO 27001 certified. SOC 2 Type 2 is currently under audit rather than complete. We do not hold a HIPAA certification and we do not sign Business Associate Agreements today. If your build depends on either, talk to us before you start.

### Keep exploring

### Ship your first bot today

$5 of free credit, self-serve API keys, and no sales call between you and your first meeting.

---

Full site index for agents: https://meetstream.ai/llms.txt
API contract (OpenAPI 3.1): https://meetstream.ai/openapi.json
MCP discovery: https://meetstream.ai/.well-known/mcp