Skip to main content
POST
/
api
/
v1
/
bots
/
{object_id}
/
resume_recording
Resume Recording
curl --request POST \
  --url https://api.example.com/api/v1/bots/{object_id}/resume_recording
{
  "id": "<string>",
  "recording_state": "<string>",
  "state": "<string>"
}
Resumes a paused recording for a bot.

Authentication

Requires API key authentication via the Authorization header.

Path Parameters

object_id
string
required
Bot ID (e.g., bot_xxxxxxxxxxx)

Response

Returns the updated bot object with recording state changed from paused to in_progress.
id
string
Bot ID
recording_state
string
Current recording state. Will be in_progress after successful resume.
state
string
Bot state (e.g., joined_recording)

Example Request

curl -X POST https://app.attendee.dev/api/v1/bots/bot_weIAju4OXNZkDTpZ/resume_recording \
  -H "Authorization: Token YOUR_API_KEY_HERE" \
  -H "Content-Type: application/json"

Error Responses

400 Bad Request

Returned when the bot is not in a valid state to resume recording (e.g., recording is not currently paused).

404 Not Found

Returned when the bot ID does not exist.

Build docs developers (and LLMs) love