REST API for Document Translation
Put Document Translation Inside Your Workflow
Upload a file, start a translation, and retrieve the result through the Lingivio REST API. Your integration uses the same processing, verification, pricing, and output pipeline as the Lingivio app.
Three Steps From Upload to Output
Every integration follows the same sequence the app follows: the file is validated and priced first, the job is started second, and the result is retrieved when the job reaches a final state.
Upload the File
Send a supported document. The response confirms the validated file type, the detected source language, and the exact credit cost before translation begins.
Start the Translation
Choose the target language and create the translation job. Use an idempotency key so a safe retry cannot create a duplicate charge.
Retrieve the Result
Poll the job status or use a signed webhook notification, then download the completed document in its original format.
Built for Reliable Document Workflows
Batch Processing
Start translations for up to 20 uploaded files in one batch. Credits are reserved for the complete batch before processing, so work cannot stop halfway because the balance ran out.
Resumable Large-File Uploads
Files larger than 25 MiB use resumable uploads, allowing an interrupted transfer to continue without restarting the entire file.
Safe Retries
Supported POST requests accept idempotency keys. Repeating the same request with the same key returns the original resource and bills once; the same key with a different body is refused rather than treated as a retry.
Stable Error Classes
Every failure includes a machine-readable class, whether the request can be retried, and what happened to any reserved credits.
Real Progress
Translation status reports real completed and total segment counts rather than a simulated percentage.
OpenAPI 3.1 Specification
Generate a client from the published OpenAPI document, which is produced from the same schemas used to validate API requests.
Open the Specification (JSON)Access and Pricing
API access is included with Business and Enterprise plans. Each file uses the same credit calculation shown in the Lingivio app, and the verified cost is returned before the translation starts.
Questions About the API, Answered
- Which Formats Does the API Support?
- The API uses the same supported formats and plan permissions as the Lingivio app, including Word, Excel, PowerPoint, PDF, image, and text formats.
- Can I Translate Several Files at Once?
- Yes. The batch endpoint accepts up to 20 previously uploaded files in a single request and starts them according to your plan's concurrency limit.
- Can the API Notify My System When a Job Finishes?
- Yes. Add a callback URL when creating the translation. Lingivio sends a signed webhook for completed, failed, or cancelled jobs and retries delivery on a backoff over several hours if your endpoint does not answer with a 2xx. If every attempt fails, the failure is recorded and you can still poll the job.
- How Long Are Uploaded Files Available?
- Files remain available within the 24-hour retention window unless you delete them earlier through the API.
Start Building With the Lingivio API
Create an API key, upload a real document, and follow the complete request sequence in the documentation.