Deepgram transcription for your meeting bots
Send a bot into any Zoom, Google Meet or Microsoft Teams call and get the transcript processed by Deepgram — selected with one field in the request, delivered by webhook.
Low-latency speech-to-text with strong streaming performance and custom model support — plug in your Deepgram key and keep your model configuration.
Select Deepgram with one field
Set the provider in transcription_config when creating the bot. Bring your own Deepgram 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": "deepgram",
"api_key": "$DEEPGRAM_API_KEY"
}
}'How Deepgram fits into Meeting BaaS
Provider-native output
When you select a non-default provider, the raw transcription artifact mirrors Deepgram's native response structure — your existing parsers keep working.
Bring your own key
Pass your Deepgram 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.
Deepgram + 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.