Recall Compat API

API Reference

Recall.ai API Compatibility Layer for Meeting BaaS

Recall.ai API Compatibility Layer

Drop-in replacement for the Recall.ai API, powered by Meeting BaaS.

Resources:

Architecture

Migration Note: Webhook URL Required

In Recall.ai, webhooks are configured at the account level through their dashboard UI. Since we don't have access to that configuration, you must provide your webhook URL in the webhook_url field when creating each bot.

POST /api/v1/bot
{
  "meeting_url": "https://zoom.us/j/123456789",
  "webhook_url": "https://your-app.com/webhooks/recall",
  "bot_name": "My Bot"
}

This URL will receive all bot lifecycle events (status changes, recording ready, transcript available) in Recall.ai webhook format.

Supported Features

  • Bot Management: Create, list, get, leave call, delete media
  • Real-time Streaming: realtime_endpoints maps to streaming_output
  • Calendar Webhooks: calendar.sync_events fully supported
  • Transcription: Gladia provider with word-level timestamps

Limitations

  • Transcription Provider: Only gladia currently. Type-safe support for AssemblyAI, Deepgram, OpenAI Whisper, Speechmatics, Azure Speech coming via VoiceRouter
  • Recording Control: Auto-starts on join; start_recording, pause_recording, resume_recording return 501
  • Chat Messages: Runtime chat not supported; use entry_message at bot creation
  • Stop Recording: Maps to leave_call (bot leaves the meeting)

Authentication

All API requests require a Meeting BaaS API key in the Authorization header:

Authorization: Token <YOUR_MEETING_BAAS_API_KEY>

Base URL

Point your Recall.ai client to this server instead of api.recall.ai:

https://api.meetingrouter.com/api/v1/

For local development:

http://localhost:8333/api/v1/

On this page