Skip to main content
GET
/
languages
/
{id}
Get a language
curl --request GET \
  --url https://api.dialnexa.com/v1/languages/{id} \
  --header 'Authorization: Bearer <token>'
{
  "id": "lang_en_us",
  "name": "English",
  "code": "en-US",
  "is_supported_for_transcription": true
}
Returns the full record for a single language supported by DialNexa. The response includes the language’s stable id, its BCP-47 code (for example en-IN, hi-IN, en-US), the human-readable display name, and the set of voices available for that language.

When to use this

Use this endpoint when you have a language id saved in your own database, on an agent configuration, or in a workflow node, and you need to resolve it to its display name, BCP-47 code, or available voice list. Common cases include:
  • Agent configuration UIs that render the selected language for a saved agent and need to show its proper name and accent options.
  • Audit and reporting tools that translate an internal language ID into a localized label for dashboards.
  • Provisioning flows that validate a language is still supported on the platform before sending an agent update through Update Agent.
If you need the entire catalogue rather than a single record, use List Languages instead. The result of that endpoint is paginated and is the canonical source of truth for what DialNexa currently supports.

Path parameters

ParameterDescription
idThe language ID, for example lang_en_in.

Errors

  • 404 Not Found is returned when the id does not match any supported language. This usually means the language has been removed from the platform or the ID was mistyped.
  • 401 Unauthorized is returned when the API key is missing, malformed, or has been revoked. See Authentication.

Request

curl "https://api.dialnexa.com/v1/languages/lang_en_in" \
  -H "Authorization: Bearer YOUR_API_KEY"

Response

{
  "id": "lang_en_in",
  "name": "English (India)",
  "code": "en-IN",
  "voices": [
    { "id": "vce_en_in_meera", "name": "Meera", "gender": "female" },
    { "id": "vce_en_in_arjun", "name": "Arjun", "gender": "male" }
  ]
}

Authorizations

Authorization
string
header
required

Pass your API key as a Bearer token in the Authorization header.

Path Parameters

id
string
required

Response

Success.

id
string
Example:

"lang_en_us"

name
string
Example:

"English"

code
string
Example:

"en-US"

is_supported_for_transcription
boolean
Example:

true