Endpoint
Authentication
Requires API key authentication via theAuthorization header.
Your API key in the format:
Token YOUR_API_KEY_HEREMust be
application/jsonQuery Parameters
Cursor for pagination. Use the cursor returned in the response to fetch the next page.
Filter bots by meeting URL.Example:
https://zoom.us/j/123456789Filter bots by deduplication key.Example:
my-unique-bot-keyFilter bots by state. Can specify multiple states.Possible values:
ready, joining, joined_not_recording, joined_recording, leaving, post_processing, fatal_error, waiting_room, ended, data_deleted, scheduled, staged, joined_recording_paused, joining_breakout_room, leaving_breakout_room, joined_recording_permission_deniedOnly return bots with
join_at after this time.Format: ISO 8601 datetime (e.g., 2024-01-18T12:34:56Z)Only return bots with
join_at before this time.Format: ISO 8601 datetime (e.g., 2024-01-18T13:34:56Z)Response
Returns a paginated list of bot objects.Cursor URL for the next page of results, or
null if no more results.Cursor URL for the previous page of results, or
null if on first page.Array of bot objects.
Unique identifier for the bot (e.g.,
bot_weIAju4OXNZkDTpZ)The URL of the meeting the bot joined or will join.
Current state of the bot.
Current transcription state (e.g.,
not_started, in_progress, complete)Current recording state (e.g.,
not_started, in_progress, complete)ISO 8601 timestamp when the bot joined or will join the meeting.
Optional deduplication key for the bot.
Custom metadata associated with the bot.
Example Request
Example Response
Error Codes
400- Invalid request parameters (e.g., invalid state, invalid date format)401- Invalid or missing API key