Retrieves a comprehensive list of all target languages supported by the platform, including their unique identifiers, language names, and corresponding short names.
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.
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.
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.
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:
/target-languages
endpoint.language
property.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.
It’s important to understand the distinction between target languages (provided by this endpoint) and source languages (provided by the /source-languages
endpoint):
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.
When working with the /target-languages
endpoint, consider these recommendations:
id
field when making API requests, rather than the language name or short name.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.
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.
Successful Response
The response is of type LanguageItem · object[]
.