Creates a new bot instance to join a meeting.
live_transcription_required field:
live_audio_required field:
recording_config parameter allows you to configure transcription providers, data retention policies, and real-time event webhooks.
recording_config.transcript.provider field. You can choose from multiple providers:
retention field:
type: "timed" (data deleted after specified hours) or (Data will be deleted after 7days )hours: Number of hours to retain data (only applicable when type is "timed")realtime_endpoints array:
participant_events.join - Triggered when a participant joins the meetingparticipant_events.leave - Triggered when a participant leaves the meetingautomatic_leave parameter configures conditions under which the bot will automatically exit the meeting. All timeout values are specified in seconds.
| Parameter | Description | Example |
|---|---|---|
waiting_room_timeout | Seconds to wait if bot is stuck in waiting room | 600 (10 minutes) |
everyone_left_timeout | Seconds to wait after all participants have left | 600 (10 minutes) |
in_call_recording_timeout | Maximum recording duration in seconds | 14400 (4 hours) |
recording_permission_denied_timeout | Seconds to wait if recording permission is denied (Zoom only) | 60 (1 minute) |
callback_url is provided in the request, the API will send POST requests to notify you about various bot status changes. Here are the events you can expect:
| Field | Type | Description |
|---|---|---|
bot_id | string | The unique identifier of the bot |
bot_status | string | Current status of the bot (joining, InMeeting, Stopped) |
message | string | Human-readable status message |
status_code | integer | HTTP-style status code indicating the event type |
audio_status | string | Status of audio processing (Success) |
transcript_status | string | Status of transcript processing (Success) |
event | string | Event type identifier (e.g., data_deletion) |
status | string | Operation status (success, failed) |
deleted_objects | integer | Number of objects deleted (data_deletion event only) |
timestamp | string | ISO 8601 formatted timestamp of the event |
102: Bot is in the process of joining the meeting200: Successful operation (joined meeting, audio/transcript processing completed, data deletion succeeded)500: Bot has stopped/exited the meeting, or data deletion failedAll API endpoints are authenticated using API Keys. The key should be included in the 'Authorization' header, prefixed with 'Token '. Example: 'Authorization: Token YOUR_API_KEY'.
Meeting URL to join.
Whether audio is required.
Whether video is required.
Message for the bot to say on join.
Live audio streaming config.
Live transcription config.
URL to the bot's profile image. Should be in the format jpeg,png,jpg,gif.
URL to the bot's socket connection. Should be in the format wss://.
The date and time the bot will join the meeting. YYYY-MM-DD HH:MM:SS Ex:2024-01-15T14:30:00Z
Callback URL for bot events.
Configuration for recording, transcription, and data retention.
Configure automatic bot exit conditions with timeout values in seconds.
Bot creation initiated successfully.
Unique identifier for the created bot.