🌍 Languages

Languages

Languages are used for LINGUISTICS services (translation, localization).

Language Categories

Languages are organized into:

  • Suggested Languages: Based on your company's previous projects and preferences

  • Other Languages: All other supported languages

Using Languages in RFQs

When creating an RFQ with LINGUISTICS services, you'll need:

  • sourceLanguageId: The language of your source content

  • targetLanguageIds: Array of languages to translate into

Language Codes

We use ISO 639-1 (2-character) codes where available, falling back to ISO 639-3 (3-character) for languages without a 2-character code.

Get available languages from the endpoints below.

🌍 Get Available Languages

get
/api/public/v1/client/languages

Get Languages for Translation Services

Retrieve available languages for your company's translation and localization projects.

Language Categories

Languages are returned in two groups:

  1. Suggested Languages: Languages your company frequently uses, based on:

    • Previous project history

    • Company language preferences

    • Most common translation pairs

  2. Other Languages: All other supported languages

Using Languages in RFQs

When creating an RFQ, use the id field from the language objects:

  • sourceLanguageId: The id of the source language (e.g., "3ebf026a-578b-46cb-b4a5-de4b54bab575")

  • targetLanguageIds: Array of id values for target languages (e.g., ["7da3f046-8d67-4cdc-beea-8e9afdaeaf30"])

Example:

{
  "serviceId": "...",
  "type": "LINGUISTICS",
  "sourceLanguageId": "3ebf026a-578b-46cb-b4a5-de4b54bab575",  ← Use the 'id' field
  "targetLanguageIds": ["7da3f046-8d67-4cdc-beea-8e9afdaeaf30"]  ← Use the 'id' field
}

Response Fields

Each language object includes:

  • id: Use this in RFQ creation - Unique language identifier (UUID)

  • name: Human-readable language name (e.g., "Danish", "English (UK)")

  • iso639Code: ISO 639 language code (can be numeric or alphanumeric)

  • isActive: Whether the language is currently active

  • createdAt: Timestamp when the language was created

  • updatedAt: Timestamp when the language was last updated

Authorizations
AuthorizationstringRequired

JWT access token obtained from POST /api/credentials/token

How to authenticate:

  1. Generate API credentials from the Adaptria Portal
  2. Exchange credentials for a token: POST /api/credentials/token
  3. Include the token in all requests: Authorization: Bearer <token>

Token Expiration: 1 hour (3600 seconds)

Query parameters
searchstringOptional

Filter languages by name or code

Responses
chevron-right
200

Languages retrieved successfully

application/json
get
/api/public/v1/client/languages

Last updated