Endpoint
Authentication
Requires API key authentication via theAuthorization header.
Your API key in the format:
Token YOUR_API_KEY_HEREMust be
application/jsonPath Parameters
The unique identifier for the bot.Example:
bot_xxxxxxxxxxxRequest Body
The
join_at, meeting_url, bot_name, bot_image, and recording_settings fields can only be updated when the bot is in the scheduled state. The metadata field can be updated at any time.The time the bot should join the meeting. Can only be updated for scheduled bots.Format: ISO 8601 datetime (e.g.,
2025-06-13T12:00:00Z)The URL of the meeting to join. Can only be updated for scheduled bots.
The name of the bot. Can only be updated for scheduled bots.
JSON object containing custom metadata. Can be updated at any time.Example:
{"customer_id": "abc123", "status": "active"}Response
Returns the updated bot object.Unique identifier for the bot.
The URL of the meeting the bot will join.
Current state of the bot.
Array of events that have occurred for this bot.
Current transcription state.
Current recording state.
ISO 8601 timestamp when the bot will join the meeting.
Deduplication key for the bot.
Custom metadata associated with the bot.
Example Request - Update join_at for scheduled bot
Example Request - Update name and image
Example Request - Update metadata
Example Response
Error Codes
200- Bot updated successfully400- Invalid input or bot cannot be updated (e.g., trying to updatejoin_atfor a bot not inscheduledstate)401- Invalid or missing API key404- Bot not found