Skip to main content
A Render combines one Character source, one Motion source, and optional background settings into a video. All Render endpoints require Authorization: Bearer YOUR_API_KEY.

Create a Render

POST /v1/renders Send multipart/form-data. For both Character and Motion, choose either a reusable ID or a direct input.

Character input

Motion input

Render settings

For each input family, send one source. For example, use character_id with a newly uploaded motion_video, or upload both inputs for a one-time Render.

Valid source combinations

bg_color is rejected unless background_mode=solid. transparent returns an additional alpha_url when ready.

Example: one-time Render

Example: reuse assets with transparent output

Python example: create and poll

Get a Render

GET /v1/renders/{render_id}
Poll every 3–5 seconds until the Render is terminal: ready, failed, or cancelled.

Ready and failed responses

Download a Render

GET /v1/renders/{render_id}/download
The endpoint redirects to the finished video. You can also download video_url from a ready Render response.

Cancel a Render

DELETE /v1/renders/{render_id} Cancel a queued or processing Render owned by the current account. If the Render is already terminal, the response reports its current terminal status.

Response and status rules

Render response fields