Fetch Translation Results in Bulk
Retrieves the final translated texts from multiple completed translation tasks using a list of run_id values in a single request.
POST
Get Translation Results
This endpoint delivers the final products of multiple translation processes simultaneously: all your translated texts in one efficient request. Once your translation tasks have completed successfully and youβve received multiple
This structured response format makes it simple to process multiple translation tasks while maintaining clear organization. You can easily access translations for any specific task or iterate through all results systematically.
run_id values, this endpoint allows you to retrieve all the actual translations that were generated. Think of it as the express pickup counter where you collect several finished translation orders at once, rather than making individual trips for each one.
How to Use This Endpoint
To retrieve multiple sets of translated texts, send aPOST request to this endpoint with an array of run_id values in the request body. Each run_id serves as your claim ticket for a finished translation task. You must provide between 2 and 5 run_id values per request. The system will respond with a structured object containing all your translated texts, organized by their corresponding run_id values.
Request Format
The request body should contain an array ofrun_id values for the completed translation tasks you want to retrieve. You must provide between 2 and 5 run_id values per request:
The
run_ids array must contain between 2 and 5 values. Requests with fewer than 3 or more than 5 run_ids will be rejected with a validation error.Understanding the Response
When you call this endpoint, youβll receive a response that includes all your translated content organized byrun_id:
results: An object where each key is arun_idand each value contains the translation data for that specific tasktexts: Within each result, an array of strings containing the translated output texts, maintaining the same order as the original input for that task
Working with Bulk Translation Results
There are several effective patterns for handling bulk translation results:Direct Processing
For immediate use, you can extract and process all translation results:Best Practices
Request Size Requirements
This endpoint requires a specific batch size for optimal performance and resource management:- Minimum: You must provide at least 2
run_idvalues per request - Maximum: You can provide up to 5
run_idvalues per request - Validation: Requests outside this range will be rejected with a validation error
Handling Larger Datasets
If you have more than 5 completed translation tasks to retrieve:- Split into Multiple Requests: Divide your
run_idlist into chunks of 3-5 items - Sequential Processing: Process chunks sequentially to avoid rate limiting
- Batch Management: Implement logic to group your run_ids efficiently
Error Recovery
Always implement proper error handling when working with bulk operations:- Check response status codes before processing results
- Handle partial failures gracefully (some run_ids may succeed while others fail)
- Implement retry logic for transient failures
- Log failed run_ids for later processing
Next Steps
Once youβve retrieved your bulk translation results, you can:- Display them to your users in organized, task-specific groups
- Store them systematically with proper task organization
- Process them further with additional NLP tools while maintaining task relationships
- Use them in your application logic to enable comprehensive multilingual functionality
Authorizations
Body
application/json
Last modified on July 15, 2025