Gladia transcription for your meeting bots
Send a bot into any Zoom, Google Meet or Microsoft Teams call and get the transcript processed by Gladia — selected with one field in the request, delivered by webhook.
The built-in default: 100+ languages, automatic language detection and speaker diarization with no provider account needed — 0.25 tokens per hour.
Select Gladia with one field
Set the provider in transcription_config when creating the bot. Bring your own Gladia API key to keep your existing account, vocabulary tuning and billing — or use the built-in Gladia default with no key at all.
curl -X POST "https://api.meetingbaas.com/v2/bots" \
-H "Content-Type: application/json" \
-H "x-meeting-baas-api-key: $API_KEY" \
-d '{
"meeting_url": "https://meet.google.com/abc-def-ghi",
"bot_name": "Transcription Bot",
"transcription_config": {
"provider": "gladia",
"api_key": "$GLADIA_API_KEY"
}
}'How Gladia fits into Meeting BaaS
Provider-native output
When you select a non-default provider, the raw transcription artifact mirrors Gladia's native response structure — your existing parsers keep working.
Bring your own key
Pass your Gladia API key in transcription_config (0.05 tokens per hour on Pro and higher plans) and keep your provider relationship, custom models and negotiated rates.
Custom parameters
Forward provider-specific options through custom_params — language hints, custom vocabulary, regional endpoints — without waiting for Meeting BaaS to wrap them.
Gladia + Meeting BaaS FAQ
Ready to ship meeting bots without building the plumbing?
Join thousands of customers that use Meeting BaaS to create AI Meeting Assistants, customer interactions analytics, and much more. Start your journey today.