Retrieves the final translated texts from multiple completed translation tasks using a list of run_id
values in a single request.
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.
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.
run_id
values for the completed translation tasks you want to retrieve. You must provide between 2 and 5 run_id
values per request:
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.run_id
:
results
: An object where each key is a run_id
and 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 taskrun_id
values per requestrun_id
values per requestrun_id
list into chunks of 3-5 itemsThe 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.
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.