Skip to main content
POST
/
api
/
v1
/
bots
/
{object_id}
/
output_video
Output Video
curl --request POST \
  --url https://api.example.com/api/v1/bots/{object_id}/output_video \
  --header 'Content-Type: application/json' \
  --data '
{
  "url": "<string>",
  "loop": true
}
'
Causes the bot to output a video through its video feed in the meeting. The video is streamed from a URL.

​
Authentication

Requires API key authentication via the Authorization header.

​
Path Parameters

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

​
Request Body

​
url
string
required
URL of the video to output. Must be a valid HTTPS URL pointing to an MP4 file.
​
loop
boolean
default:"false"
Whether to loop the video. Defaults to false for single playback.

​
Response

Returns a 200 status code when the video request is successfully created.

​
Example Request

curl -X POST https://app.attendee.dev/api/v1/bots/bot_weIAju4OXNZkDTpZ/output_video \
  -H "Authorization: Token YOUR_API_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/video.mp4",
    "loop": true
  }'

​
Example Non-Looping Video

curl -X POST https://app.attendee.dev/api/v1/bots/bot_weIAju4OXNZkDTpZ/output_video \
  -H "Authorization: Token YOUR_API_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/presentation.mp4"
  }'

​
Error Responses

​
400 Bad Request

Returned when:
  • Invalid URL format
  • URL does not point to a valid MP4 file
  • Missing required fields
  • Bot is not in a valid state to output video

​
404 Not Found

Returned when the bot ID does not exist.
The video must be accessible via HTTPS and in MP4 format. The bot will stream this video through its video feed in the meeting.

Build docs developers (and LLMs) love

Get started for freeTalk to us