Skip to main content
GET
Get Translation Result
This endpoint delivers the final product of your translation process: the translated texts themselves. Once your translation task has completed successfully and you’ve received a run_id, this endpoint allows you to retrieve the actual translations that were generated. Think of it as the pickup counter where you collect your finished translations after they’ve been processed.

How to Use This Endpoint

To retrieve your translated texts, send a GET request to this endpoint with the run_id you received when your translation task was marked as completed. This run_id serves as your claim ticket for the finished translations. The system will respond with an array containing all your translated texts, preserving the same order as your original input.

Understanding the Response

When you call this endpoint, you’ll receive a response that includes your translated content:
  • texts: An array of strings containing the translated output texts. Each item in this array corresponds to one of the original texts you submitted, maintaining the same order. This makes it easy to match translations with their original content.
The structure of the response follows this format:
This straightforward response structure makes it simple to integrate translations into your application workflows. You can directly map each translated text to its corresponding original text by using the same array indices.

Working with Translation Results

There are several common patterns for handling translation results effectively:

Direct Integration

For immediate use, you can simply extract the texts array and use the translations in your application:

Parallel Display

For applications that need to show both original and translated text together, you can zip the arrays:

Saving to Database

For longer-term storage, you might want to save the translation results alongside their originals:

Next Steps

Once you’ve retrieved your translations, you can:
  1. Display them to your users
  2. Store them for future reference
  3. Process them further with additional NLP tools
  4. Use them in your application logic to enable multilingual functionality
The simplicity of the response format makes it easy to integrate translations wherever they’re needed in your workflow, whether you’re building a multilingual website, an educational app, or an international communication tool. By understanding how to effectively use this endpoint, you can create smoothly functioning multilingual applications that deliver high-quality translations to your users at exactly the right moment in their journey.

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.

Path Parameters

run_id
integer
required

The unique identifier for the run, which was generated during the translation creation process and returned upon task completion. The unique identifier for the run, which was generated during the creation process and returned upon task completion.

Response

Successful Response

texts
string[]

An array of strings containing the translated output texts. Each item in the array corresponds to one translated text