Google Meet Recording API to Record Any Meet Call
A Google Meet recording API puts a named bot in the call and returns an MP4, plus audio and video for every participant. From $0.35 per bot-hour.
*Get started in minutes*
What is a Google Meet recording API?
A Google Meet recording API captures a live Meet call from your code. One request, and an MP4 arrives at a URL when the meeting ends.
A named bot joins from the meeting link and records what it receives. The meeting recording API covers all three platforms.
What you get from every Google Meet recording
One request in. An MP4, a stream for every participant, and the events that say they are ready.
*Get started in minutes*
What a Google Meet recording contains
| Artefact | On Google Meet |
|---|---|
| Per-participant audio | Partial isolation. Meet gives up to three speaker streams at once, each tied to the active speaker. Clean for normal turn-taking, approximate under cross-talk. |
| Per-participant video | Webcam up to 854 by 480 at 800 kbps; screen share up to 1280 by 720 at 2 Mbps; multiple concurrent screen shares |
| Composed recording | Composed MP4 and a mixed WAV, always produced. Pause and resume during the call |
| Real-time audio | 48 kHz PCM16 frames with speaker ID and name over your WebSocket, typically under 200 ms |
| Participants | Join and leave events with stable IDs. Names settle in about ten seconds after a join |
Meet gives three speaker streams at once, tied to the active speaker. The per-participant audio entry explains the model.
Which Google Meet rules affect recording?
Meet's rules are mostly about admission and edition. Each one links to Google's own documentation.
| Google Meet rule | What it means for a bot |
|---|---|
| Native recording editions | Limited to that include it. Recording also stops after eight hours. |
| Bots and admission | With "Anyone can ask to join" unchecked, third-party bots are automatically denied access. |
| Access types | Open, Trusted and Restricted decide who has to knock before joining. |
| Consent | Admins can require Gemini notes consent, and anyone who declines is removed. |
| Admin guidance | An admin article titled "External apps are recording Meet meetings" lists blocking app domains. |
How a bot is admitted to Google Meet
A guest bot knocks, and someone in the call admits it. Under host management, hosts and co-hosts are the people who see that request.
Meet admits and records in one step. Participant events tell your app whether it is waiting, inside or on its way back out.
| Meeting access setting | What the bot sees | Event you receive |
|---|---|---|
| Open | Joins directly | bot.inmeeting, then bot.recording |
| Trusted (default) | Knocks and waits. Only hosts and co-hosts see the request, under host management | bot.in_waiting_room, then bot.inmeeting or bot.notallowed after waiting_room_timeout (600 s) |
| Restricted, or anonymous users blocked | Guest bot is refused | bot.denied; use a signed-in bot from an allowed domain |
| Bot on the invite as a signed-in account | Usually enters without knocking | bot.inmeeting |
From a Google Meet link to your product
One request puts a bot in the call. It records while the meeting runs, then a webhook says the files are ready.
*Get started in minutes*
Record a Google Meet meeting with one request
Post the meeting link. The bot joins, records, and fires a webhook when the call ends.
curl -X POST https://api.meetstream.ai/api/v1/bots/create_bot \
-H "Authorization: Token $MEETSTREAM_API_KEY" \
-d '{
"meeting_link": "https://meet.google.com/abc-defg-hij",
"bot_name": "Acme Notetaker",
"audio_separate_streams": true,
"video_separate_streams": true,
"callback_url": "https://your-app.example.com/meetstream"
}'Which Google API records a Meet call?
Google has native surfaces of its own, and a recording bot sits above all of them.
*Get started in minutes*
The Meet REST API returns the recordings and transcripts Meet itself produced, so it carries the edition rules with it.
A bot behaves the same way on any Meet account. The Google Meet bot API page sets both routes side by side.
Where Google Meet recordings are stored
Recordings are kept for thirty days by default. Connect your own S3 bucket and every artefact lands in your account from the first byte.
Your lifecycle rules, object lock and retention schedule then govern the record. Bots run in the United States by default.
The Google Meet integration page covers signed-in bots, which join as named Workspace users.
Google Meet recording API pricing
A recording bot costs $0.35 per bot-hour. Transcription adds $0.10, and the rate falls toward $0.25 at volume.
Thirty days of storage is included, and every account starts with $5 of free credit. The pricing page has the full breakdown.
The comparison hub sets MeetStream beside the other meeting bot vendors, on their own published rates.
Google Meet recording limits and defaults
Participant events tell your app the moment the bot is admitted, so your user always sees the real status.
One integration for all three platforms
The same request, the same webhook, the same files. Only the link changes.
Google Meet recording from a link, on any account.
One request records the call, whatever Workspace edition the host is on.
*Get started in minutes*
Got a question? We got the answer.
Common questions about recording Google Meet calls. What comes back, who admits the bot, and what it costs.
*Get started in minutes*
Can I record a Google Meet call I do not host?
Yes, from the link. The bot joins as a guest and someone in the meeting admits it. On strict domains a signed-in bot joins as a named Workspace user.
Can I record Google Meet without a Workspace edition that includes recording?
Yes. Native recording is limited to specific Workspace editions. A bot joins as a participant and records independently of the host's edition.
Do Google Meet participants know a bot is recording?
Yes. Meet shows every participant, so the bot has a visible tile under the name you choose. Post a joining message and the room knows what is recording.
Can I get separate audio for each Meet participant?
Meet gives up to three speaker streams at once, each tied to the active speaker. That is exact through normal turn-taking and close during cross-talk.
What format is a Google Meet recording returned in?
A composed MP4 of the meeting, a mixed WAV track, and per-participant video with webcam up to 854 by 480 and screen share up to 1280 by 720.
How long can a Meet recording bot stay in a call?
Four hours by default, and five hours once you raise the session setting. Concurrency is open, so run as many bots as your product needs.
How long are Google Meet recordings stored?
Thirty days by default. Connect your own S3 bucket and every artefact lands in your account from the first byte, under your own retention policy.
How much does the Google Meet recording API cost?
$0.35 per bot-hour, or $0.45 with transcription, falling toward $0.25 at volume. Thirty days of storage is included and every account starts with $5 of credit.
Record your next Google Meet call
$5 of free credit, self-serve API keys, and no sales call between you and your first recording.