Skip to main content
Characters and Motions are reusable asynchronous assets. Renders and 3D Conversion requests are asynchronous operations that deliver artifacts.

Status lifecycle

cancelled applies to Render state; clients should treat it as terminal. Poll every 3–5 seconds while a resource is queued or processing. Stop polling for ready, failed, or cancelled.

Polling example

Render progress

Render responses can include:
  • progress: an integer from 0 to 100
  • stage: analyzing, rendering, or finishing
  • video_url: available only when the Render is ready
  • alpha_url: available with transparent output

Download promptly

Completed result URLs and task state are retained for one hour. Persist output in your own storage if it is needed later.

Recover safely

  • For failed, inspect error.code and follow its suggested recovery path.
  • Do not retry a Render blindly after a network timeout: V1 does not currently expose idempotency keys. If a create response was received, query its known resource ID; otherwise resolve the outcome with your request logs and X-Request-Id before submitting again.
  • Include X-Request-Id in support requests.