Skip to main content

Overview

Translation batches let you submit many translations in one request instead of calling POST /v3/video-translations once per job. Each item is a standard translation payload, the exact shape that endpoint accepts, so anything you can translate 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. A single payload targeting multiple output_languages expands to one batch item per language, and the expanded count is what the 100-item cap applies to. Each item is created and processed independently, so one bad source does not fail the rest.

Create a Batch

POST /v3/video-translations/batches takes the payloads in video_translations. One source video fanned out to three languages creates three batch items:
Each entry takes the full set of translation options: video (as a url or asset_id), output_languages (use GET /v3/video-translations/languages for valid values), mode (speed or precision), plus captions, brand glossary, stock voice, partial-range, and format controls.

Get a Batch

Poll GET /v3/video-translations/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 translation batches it holds the video translation id. Use it with GET /v3/video-translations/{video_translation_id} for the full record and download URL.

Bulk Statuses

GET /v3/video-translations/statuses checks up to 100 translations in one request, across batches or for jobs created individually. Pass comma-separated video_translation_ids, or batch_ids (each expands to its member translations). Statuses are queued, processing, completed, or failed, plus not_found for unknown or unowned ids.

Tracking completion

Besides the batch callback_url and polling, you can subscribe to video_translate.success / video_translate.fail webhook events for per-item notifications. Items surface their translation id as soon as the job is created, so you can start fetching finished translations while the rest of the batch is still processing.