Get a Google Meet transcript via API

​

1. Send the bot

curl -X POST "$API_BASE/bots" \
  -H "X-API-Key: $API_KEY" -H "Content-Type: application/json" \
  -d '{"platform":"google_meet","native_meeting_id":"abc-defg-hij","bot_name":"Vexa"}'

curl -X POST "$API_BASE/bots" \
  -H "X-API-Key: $API_KEY" -H "Content-Type: application/json" \
  -d '{"meeting_url":"https://meet.google.com/abc-defg-hij","bot_name":"Vexa"}'

​

2. Read the transcript live

curl -H "X-API-Key: $API_KEY" \
  "$API_BASE/transcripts/google_meet/abc-defg-hij"

{
  "segments": [
    { "speaker": "Jane Liu", "text": "Let's lock the renewal pricing by July 1.",
      "start": 12.4, "end": 15.1, "language": "en", "completed": true, "confidence": 0.93 }
  ]
}

{ "action": "subscribe",
  "meetings": [ { "platform": "google_meet", "native_id": "abc-defg-hij" } ] }

​

Google Meet specifics

• Admission. The bot may be parked in a lobby until a host admits it — admit it like any guest. A run that ended there reports awaiting_admission_timeout or awaiting_admission_rejected; automatic_leave.max_wait_for_admission sets how long it waits.
• Joining as a real account. With authenticated: true the bot uses a persistent browser profile and joins as your Google account instead of an anonymous guest. If that profile is signed out it refuses to join with auth_session_missing rather than silently degrading — see Authenticated bots.
• Leaving on its own. An active bot leaves after 10 minutes with no remote microphone audio and finishes as completed(left_alone). Widen it per meeting with automatic_leave.max_time_left_alone.

​

Stop the bot

curl -X DELETE "$API_BASE/bots/google_meet/abc-defg-hij" -H "X-API-Key: $API_KEY"

​

See also

• Send a bot and get a transcript — the full walkthrough, all platforms
• Meetings API — every parameter, status, and response shape
• Troubleshooting — the bot joined but there is no transcript