EnginesHow it worksDocumentation
Console

v1

Errors & limits

Submit a video and audio. Receive a webhook or poll for status and download the result

Error response — HTTP 429
{"error":{"code":"RATE_LIMITED","message":"customer request rate exceeded","retryable":false}}
400

Invalid JSON, input formats or request fields

401

Missing, invalid or revoked API key

402

Insufficient demo credit to start a render

403

Private demo access denied

404

Missing or inaccessible resource; foreign resources are hidden

405

HTTP method not supported for this endpoint

409

Idempotency or immutable identity conflict, or a referenced input is not ready

410

Expired input or record

413

Request exceeds the 64 KiB JSON body cap

429

Request rate or concurrent-render limit exceeded

503

Service or selected engine temporarily unavailable

A 429 response includes Retry-After: 60. Wait before retrying; keep the same idempotency key for the same render request. The retryable field describes the returned error and does not replace the HTTP status or retry headers


Default account limits are 60 requests per minute and two concurrent renders. Administrators can configure these limits. Idempotency records are retained for six days. Terminal render records expire after 29 days; output objects have a 30-day storage lifecycle policy. Downloads use 15-minute signed URLs, refreshed by fetching the render

Invalid source media or engine failures may be reported asynchronously in the render and webhook rather than as an HTTP error from the initial accepted request