Skip to main content
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 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 a POST 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 of run_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 by run_id:
  • results: An object where each key is a run_id and each value contains the translation data for that specific task
  • texts: Within each result, an array of strings containing the translated output texts, maintaining the same order as the original input for that task
The structure of the response follows this format:
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.

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_id values per request
  • Maximum: You can provide up to 5 run_id values 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_id list 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:
  1. Display them to your users in organized, task-specific groups
  2. Store them systematically with proper task organization
  3. Process them further with additional NLP tools while maintaining task relationships
  4. Use them in your application logic to enable comprehensive multilingual functionality
The structured response format makes it easy to integrate multiple translation results wherever they’re needed in your workflow, whether you’re building a multilingual content management system, an educational platform with batch translation capabilities, or an international communication tool that processes multiple conversation threads. By understanding how to effectively use this bulk endpoint, you can create highly efficient multilingual applications that deliver multiple sets of high-quality translations to your users in a single, streamlined operation.

Authorizations

x-api-key
string
header
required

The x-api-key is a custom header required for authenticating requests to our API. Include this header in your request with the appropriate API key value to securely access our endpoints. You can find your API key(s) in the 'API' section of our studio website.

Body

application/json
run_ids
integer[]
required

An array of unique positive integers, each representing the ID of a specific run. You must provide between 2 and 5 IDs, and all IDs must correspond to the same run type (e.g., all text-to-speech or all dubbing runs).

Required array length: 2 - 5 elements
Example:

Response

Successful Response

An object containing the results of one to five transcription runs. Each key in the object is a unique identifier for a run, and the corresponding value is the translation output.

{key}
Translation Result Β· object