Endpoint
Authentication
Requires API key authentication via theAuthorization header.
Your API key in the format:
Token YOUR_API_KEY_HEREMust be
application/jsonRequest Body
The URL of the meeting to join.Example:
https://zoom.us/j/123?pwd=456The name of the bot.Example:
My BotJSON object containing custom metadata to associate with the bot.Example:
{"customer_id": "abc123", "user": "john_doe"}The time the bot should join the meeting. If not specified, the bot will attempt to join immediately.Format: ISO 8601 datetime (e.g.,
2025-06-13T12:00:00Z)The ID of the calendar event the bot should join.
Optional key for deduplicating bots. If a bot with this key already exists in a non-terminal state, the new bot will not be created and an error will be returned.
List of webhook subscriptions to create for this bot.Each item should have:
url(string): The webhook URL (must be HTTPS)triggers(array): List of trigger types (e.g.,bot.state_change,transcript.update)
The transcription settings for the bot.Example:
{"deepgram": {"language": "en"}}Response
Returns the created bot object.Unique identifier for the bot (e.g.,
bot_weIAju4OXNZkDTpZ)The URL of the meeting the bot will join.
Current state of the bot (typically
joining or scheduled).Array of events that have occurred for this bot.
Current transcription state (typically
not_started for new bots).Current recording state (typically
not_started for new bots).ISO 8601 timestamp when the bot will join the meeting.
Deduplication key for the bot, if provided.
Custom metadata associated with the bot.
Example Request
Example Response
Error Codes
201- Bot created successfully400- Invalid input (e.g., invalid meeting URL, missing required fields, bot with same deduplication key already exists)401- Invalid or missing API key