Create Document Translation Job
Document Translation
Create a document translation job. Returns a job_id and a short-lived signed upload_url.
Flow:
POST /translate/document/jobswith source/target languages and options.PUTthe raw file bytes toupload_urlwith headerContent-Type: <mime>.POST /translate/document/jobs/{job_id}/startto begin the pipeline.- Poll
GET /translate/document/jobs/{job_id}/live-statusuntil translation completes. POST /translate/document/jobs/{job_id}/export?lang=<code>to enqueue an async export for each target language (exports in the uploaded file’s format by default).- Poll
GET /translate/document/jobs/{job_id}/export/statusuntilexport_stateisCompleted, then download fromdownload_url.
A single job translates into every language in target_language_codes. Exports run asynchronously — do not expect the download URL in the trigger response.
Authentication
Request
Source language (BCP-47).
Original filename with extension. Supported: .pdf, .doc, .docx, .odt, .xls, .xlsx, .ods, .ppt, .pptx, .odp, .html, .xhtml, .mhtml.
Target languages (BCP-47).
Optional human-readable job name. Defaults to original_filename when omitted.
Genre enum name (e.g. NON_FICTION). Use the enum constant name, not the human-readable label.
use_native_numerals is an optional parameter with three options:
null(default): Uses the application default.false: Uses international numerals (0-9).true: Uses language-specific native numerals.
Example:
- If international numerals are used, numbers appear as regular digits (0-9). For example:
मेरा phone number है: 9840950950. - If native numerals are used, numbers appear in the target script. For example:
मेरा phone number है: ९८४०९५०९५०.
Global tone, terminology, and formatting instructions (up to ~4000 characters). Applies to every target language.
Per-language overrides (up to ~4000 characters each). Keys must match entries in target_language_codes.