EN
Meeting APIClosed beta

Google Meet Recording and Transcription API

Record, transcribe and summarise Google Meet calls from your own product. Post a meet.google.com link and get the recording, speaker-attributed transcript, summary and action items back by webhook.

In closed beta. Contact us to get access.

Native API vs notetaker

What the Google Meet API can and cannot record

The Meet REST API lists recordings and transcripts that Google Workspace already generated. The Meet Media API adds real-time media under its own rules. A notetaker captures the meeting itself.

Google Meet logoMeet REST API Google Meet logoMeet Media API Unipile notetaker
What you get Meet REST APIRecordings and transcripts generated by Google Workspace Meet Media APIReal-time audio and video media Unipile notetakerRecording, speaker-attributed transcript, summary and action items
Who starts it Meet REST APINative recording or transcription enabled in Meet Meet Media APIYour own client, connected to the live conference Unipile notetakerYour product, with one request or a calendar event
When data arrives Meet REST APIAfter the meeting, once Google has generated the artifacts Meet Media APILive, during the call Unipile notetakerLifecycle and artifact webhooks, as each one is ready
Conditions Meet REST APIDepends on the meeting, the Workspace edition and organiser permissions Meet Media APIDeveloper preview, with its own eligibility, scopes and consent requirements Unipile notetakerA meeting URL and your user's connected Google account

Google documentation checked on November 12, 2026.

Request and webhook

Record a Google Meet call with one request

The provider is inferred from the meet.google.com URL. Nothing else in the payload is Google-specific: the same request works for Microsoft Teams and Zoom. Full reference in the developer docs.

Requestrecord-meet.sh
curl --request POST \
  "https://api.unipile.com/v2/$ACCOUNT_ID/notetakers" \
  --header "X-API-KEY: $UNIPILE_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "meeting_url": "https://meet.google.com/abc-defg-hij",
    "bot_name": "Acme CRM Notetaker",
    "capture_settings": {
      "audio_recording": true,
      "video_recording": false
    },
    "artifact_settings": {
      "transcript": { "enabled": true },
      "summary": { "enabled": true }
    }
  }'
Webhooknotetaker.transcript
{
  "object": "Event",
  "id": "evt_01k0000000000000000000000",
  "created_at": "2026-10-14T09:42:12.000Z",
  "type": "notetaker.transcript",
  "account_id": "acc_01k00000000000000000000",
  "hash": "a-stable-event-hash",
  "payload": {
    "notetaker_id": "nt_01k00000000000000000000000",
    "status": "available"
  }
}

Instant join

Your user clicks Record: the notetaker asks to join the ongoing call within seconds.

Scheduled join

Send join_at with the meeting start time and the notetaker is dispatched on time.

From Google Calendar

Matching events schedule their own notetaker. See automatic meeting recording.

Admission on Meet

Waiting room, external guests and capture strategies on Meet

A guest joining a call inside a Workspace domain can wait in the lobby until a host admits it, and some domains refuse external participants altogether. Two ways out, behind the same request.

Cloud capture

A hosted participant knocks on the call. The job stays in joining and its history says it is waiting for admission, so your UI can prompt the user instead of timing out.

Extension capture

The Meet tab is captured in the browser of a participant already in the call. No external guest, nothing for the host to accept.

Auto or pinned

auto tries the configured sources in order. Pin cloud or extension when a security review approved only one. More on capture strategies in the Notetaker API overview.

Meeting artifacts

What you get from a Google Meet capture

Audio and video

Meeting media served with HTTP Range support, so your player can seek instantly instead of downloading a full MP4.

Speakers, not channels

Timestamped segments attributed to named participants, with automatic language detection. Format details in the meeting transcription API.

Summary and action items

Generated from the final transcript with your own instructions: one format for sales calls, another for support reviews.

One account model

One Google connection for Meet, Gmail and Calendar

The notetaker runs on the Google account your user already connected for the Gmail API and the Google Calendar API. No second OAuth screen, no second consent to explain.

For a CRM or an ATS, the Meet transcript, the email thread and the calendar event arrive on the same Unipile account, ready for the same record. Same model on every platform of the Notetaker API.

Google Meet recording API: frequently asked questions

Native Meet APIs, transcripts, admission and consent, answered for developers.

Google's Meet REST API exposes recordings and transcripts generated by supported Google Workspace workflows, while its Meet Media API has separate eligibility, scope and consent requirements. The Unipile notetaker captures the meeting itself and returns the recording, transcript, summary and action items through one contract.

On Google's side, what the Meet REST API can return depends on the Workspace edition, organiser permissions and native recording or transcription being enabled. On Unipile, the notetaker costs €0.30 per hour of capture, transcript included, with 5 hours free per connected account each month. Details on the meeting bot API pricing page.

The Meet REST API returns transcripts that Google Meet generated, when transcription was turned on. The Unipile notetaker returns its own speaker-attributed transcript with timestamps and automatic language detection, delivered by the notetaker.transcript webhook. Format details in the meeting transcription API.

Either read the artifacts Google generated through the Meet REST API, when native recording was enabled, or send a notetaker with POST /v2/{account_id}/notetakers and the meet.google.com URL. The recording is served with HTTP Range support once the notetaker.recording webhook arrives.

With the cloud strategy, when the Workspace domain requires host admission, the job stays in joining and its history reports that it is waiting in the lobby, so your interface can prompt the user to admit it. With the extension strategy, no external guest joins, so there is nothing to admit.

Yes, as long as your user legitimately attends the meeting, for example as an invited participant, and participants are informed as required by the applicable law.

Still have questions? Our team is here to help.

Talk to an expert