GET
/
target-languages
Get Target Languages
curl --request GET \
  --url https://client.camb.ai/apis/target-languages \
  --header 'x-api-key: <api-key>'
[
  {
    "id": 123,
    "language": "<string>",
    "short_name": "<string>"
  }
]
This endpoint serves as your gateway to the multilingual output capabilities of our platform, providing a complete catalog of all languages that can be used as target languages in translation, text-to-speech, and other language processing operations. By querying this endpoint, you’ll receive detailed information about each supported language, enabling you to make informed choices when implementing multilingual features in your applications.

​
Understanding Target Languages

Target languages represent the destination in language transformation processes. When you translate content, the target language is the language into which your content will be converted. Having accurate information about available target languages is fundamental to ensuring your application correctly delivers content to your diverse user base.

​
How to Use This Endpoint

To retrieve the list of supported target languages, simply send a GET request to this endpoint. No parameters are required, as the response will include all available target languages. The system will respond with an array containing detailed information about each language.

​
Understanding Language Identifiers

The language identifiers returned by this endpoint are crucial for other API operations. When you make requests to endpoints like /translate, you’ll need to specify the target language using the id value. This creates a consistent system for language identification across the entire API. Here’s how the language identifiers connect different parts of the API ecosystem:
  1. Fetch available languages using the /target-languages endpoint.
  2. Present choices to your users in a meaningful way using the language property.
  3. Submit requests to other endpoints using the id property as the language identifier.
This workflow ensures that your application always uses valid language values that the API can understand and process correctly.

​
Relationship with Source Languages

It’s important to understand the distinction between target languages (provided by this endpoint) and source languages (provided by the /source-languages endpoint):
  • Target languages are languages that your content can be translated into.
  • Source languages are languages that your content starts in.
While there is often significant overlap between these sets, they are not always identical. Some languages may be available as target languages but not as source languages, or vice versa. For comprehensive multilingual applications, you should check both endpoints to understand the full range of language transformations available to you.

​
Best Practices

When working with the /target-languages endpoint, consider these recommendations:
  1. Cache the results: Since language lists change infrequently, store the response locally and refresh it periodically (e.g., once a day) rather than making a request every time a user interacts with your application.
  2. Sort languages appropriately: In user interfaces, consider sorting languages alphabetically or by relevance to your user base.
  3. Use appropriate identifiers: Always use the id field when making API requests, rather than the language name or short name.
  4. Provide search functionality: For applications with many language options, implement search or filtering to help users quickly find their desired language.
  5. Display language variants clearly: When presenting language options to users, ensure variants of languages (e.g., Brazilian Portuguese vs. European Portuguese) are clearly distinguished.
By leveraging this endpoint effectively, you can create truly global applications that deliver content in users’ preferred languages, enhancing accessibility and user experience across diverse audiences.

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.

Response

200
application/json

Successful Response

The response is of type LanguageItem · object[].