Zoom
Transcription
API
Vexa joins Zoom as a guest, and the host decides whether it gets in. The transcript comes back over REST or WebSocket.
- Zoom call
- Vexa bot
- Transcripts
- Your app
- REST · WebSocket
Your agents read the meeting while it runs.
The transcript streams to your agents as people speak, over WebSocket or MCP.
Built for Zoom
You don't need a Zoom Pro plan or cloud recording, and you don't publish a Marketplace app.
- Send the numeric meeting ID or the meeting link
- Read speaker-attributed segments over REST, or stream them over WebSocket
- Apache 2.0: self-host it, with your own transcription
# From https://us05web.zoom.us/j/81234567890?pwd=...
# native_meeting_id = "81234567890"
# (or send the whole link as "meeting_url"; a passcode in it is read too)
curl -X POST "$API_BASE/bots" \
-H "Content-Type: application/json" \
-H "X-API-Key: $API_KEY" \
-d '{
"platform": "zoom",
"native_meeting_id": "81234567890",
"bot_name": "Vexa"
}'
# Read the transcript, during or after the meeting
curl "$API_BASE/transcripts/zoom/81234567890" \
-H "X-API-Key: $API_KEY"$API_BASE to https://api.cloud.vexa.ai (hosted) or http://localhost:18056 (self-host). Get $API_KEY from /start.Common patterns
What you can build with the Zoom API
Three things you can build on the Zoom API.
Transcripts in your app
Your product works on customers' Zoom calls and needs the transcript, live or right after.
- Send a bot from the meeting link.
- Stream segments over WebSocket and store them yourself.
- A signed webhook says when the meeting ends.
Research and discovery calls
Product and research teams interview customers on Zoom and want each transcript by speaker.
- An n8n workflow sends the bot from the calendar.
- It fetches the transcript when the meeting ends.
- Check speaker names on Zoom before you rely on them.
Call review
Managers review recorded sales or client calls to see what worked.
- Vexa keeps the recording and the transcript of each call.
- Your review tool or agent reads them through the API.
Send a bot to a Zoom call
From an API key to a transcript: no SDK to install and no marketplace app to approve.
Quickstart
- Get an API keySign in at vexa.ai. Self-hosted:
make allprints a key. - Take the meeting IDFrom https://us05web.zoom.us/j/81234567890, the
native_meeting_idis 81234567890. - POST /botsSend platform
zoomwith the ID. No Marketplace approval. - Admit the botWith a waiting room, the host admits the bot.
- Read the transcript
GET /transcripts/zoom/{native_meeting_id}, or subscribe over WebSocket.
Zoom architecture
In 0.12 the bot joins through the Zoom web client, in its own container.
Documentation
Go deeper on Zoom
Reference docs for the Zoom buyer: URL formats, lifecycle, webhooks, self-host, diarization.
- Zoom transcript APIMeeting IDs, passcodes, the web client and reading the transcript.
- Send a botThe POST /bots call on every platform.
- Stream a transcriptSegments over WebSocket while the meeting runs.
- WebhooksA signed event when a meeting starts, ends or fails.
- Completion reasonsWhy a bot left, and which side it points at.
- AuthenticationAPI keys and scopes.
Full reference at docs.vexa.ai.
Related reading
Keep going on Zoom
Related pages, guides and comparisons.
Zoom transcription FAQ
Things developers and buyers usually want to know before they wire Zoom up.
Do I need a Zoom Pro plan or cloud recording?
No. Zoom's own transcription depends on the host's plan and cloud-recording settings. Vexa joins as a participant, captures the audio and transcribes it separately, so the plan doesn't matter. The host still decides whether the bot is admitted.
Do I need to publish a Zoom Marketplace app?
No. In 0.12 Vexa joins through the Zoom web client only, with no Marketplace listing, OAuth app or SDK credentials.
How does this compare to Zoom AI Companion?
AI Companion is built into Zoom and keeps its notes there. Vexa is an API across Zoom, Teams and Meet: you send a bot and read the transcript while people talk, and self-hosted it stays on your own systems.
How well does Vexa name speakers on Zoom?
Less well than on Google Meet and Microsoft Teams: some segments come back with no speaker name. If you need per-speaker attribution on Zoom, test it on your own meetings first.
A seat, an hour, or free
A seat for your agent. An hour for what you build. No licence fee when you run it yourself.
Start with Zoom. Read the transcript as it happens.
Sign in, copy an API key, send a bot with the meeting link, read the transcript. Free credit, no card.
Apache 2.0 · Self-host or cloud · No credit card required