Skip to main content

Overview

Lipsync batches let you submit many lipsync jobs in one request instead of calling POST /v3/lipsyncs once per job. Each item is a standard lipsync payload, the exact shape that endpoint accepts, so anything you can lipsync on its own can be batched, in either Speed or Precision mode. Batch mechanics (202 Accepted, title, callback_url, Idempotency-Key, the batch read model and pagination) match video batches.
A batch holds up to 100 items. Each payload becomes exactly one batch item, and each item is created and processed independently, so one bad source does not fail the rest.

Create a Batch

POST /v3/lipsyncs/batches takes 1 to 100 payloads in lipsyncs:
Each entry takes the full set of lipsync options: video and audio (each as a url or asset_id), mode (speed or precision), plus captions, partial-range, and format controls.

Get a Batch

Poll GET /v3/lipsyncs/batches/{batch_id}. The response shape matches the video batch.
The batch read model is shared across the batch APIs, so the per-item id field is named video_id. For lipsync batches it holds the lipsync id. Use it with GET /v3/lipsyncs/{lipsync_id} for the full record and download URL.

Bulk Statuses

GET /v3/lipsyncs/statuses checks up to 100 lipsyncs in one request, across batches or for jobs created individually. Pass comma-separated lipsync_ids, or batch_ids (each expands to its member lipsyncs). Statuses are queued, processing, completed, or failed, plus not_found for unknown or unowned ids. Items surface their lipsync id as soon as the job is created, so you can start fetching finished renders while the rest of the batch is still processing.