> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Get Language Details
> Fetch one supported language by ID.
Read only
**Recommended.** This endpoint is part of the public `/v1` API reference and is the supported path for new integrations. See the [migration guide](/docs/api-reference/v1/migrating-to-v1) for versioning guidance.
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](/docs/api-reference/v1/agents/update).
If you need the entire catalogue rather than a single record, use [List Languages](/docs/api-reference/v1/languages/list) instead. The result of that endpoint is paginated and is the canonical source of truth for what DialNexa currently supports.
## Path parameters
| Parameter | Description |
| --------- | ------------------------------------------ |
| `id` | The 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](/docs/api-reference/authentication).
## Related endpoints
* [List Languages](/docs/api-reference/v1/languages/list): fetch every language the platform supports.
* [List Voices](/docs/api-reference/v1/voices/list): list voices filterable by language code.
* [Update Agent](/docs/api-reference/v1/agents/update): change the language assigned to an existing agent.
## OpenAPI
````yaml GET /v1/languages/{id}
openapi: 3.0.0
info:
title: DialNexa API
description: >-
Public REST API for the DialNexa voice AI platform. Versioned endpoints are
under /v1; unversioned endpoints are legacy and deprecated.
version: 1.0.0
servers:
- url: https://api.dialnexa.com
description: DialNexa production API
security:
- bearer: []
tags:
- name: API Keys
- name: Agent Functions
- name: Agents V1
- name: Agents2
- name: Batch Calls
- name: Batch Calls V1
- name: Call Logs
- name: Calls
- name: Calls V1
- name: Campaign Leads
- name: Campaigns
- name: External Webhooks
- name: Knowledge Base
- name: Knowledge Base V1
- name: LLMs
- name: LLMs V1
- name: Languages
- name: Languages V1
- name: Organization Phone Numbers
- name: Organization Phone Numbers V1
- name: Phone Number Pricing
- name: Phone Number Pricing V1
- name: Transcribers
- name: Transcribers V1
- name: User Webhooks
- name: User Webhooks V1
- name: V1
- name: Voices
- name: Voices V1
- name: Webcall
- name: Workflow Leads
- name: Workflow Leads V1
- name: Workflows
- name: Workflows V1
paths:
/v1/languages/{id}:
get:
tags:
- Languages V1
- V1
summary: Get Language Details
description: Returns one language catalog record by ID.
operationId: LanguagesV1Controller_findOne
parameters:
- name: id
required: true
in: path
description: Language ID
schema:
example: lang_abc123
type: string
responses:
'200':
description: Language returned successfully.
content:
application/json:
schema:
$ref: '#/components/schemas/Languages'
examples:
success:
summary: Successful response
value:
id: lang_en_in
name: English (India)
code: en-IN
'400':
description: Invalid catalog ID format.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
examples:
error:
summary: 400 Bad Request
value:
statusCode: 400
message: Invalid catalog ID format
error: Bad Request
'401':
description: Unauthorized.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
examples:
error:
summary: 401 Unauthorized
value:
statusCode: 401
message: API key is missing or invalid
error: Unauthorized
'403':
description: Forbidden - API key does not have access to this organization.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
examples:
error:
summary: 403 Forbidden
value:
statusCode: 403
message: You do not have permission to access this resource
error: Forbidden
'404':
description: Language not found.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
examples:
error:
summary: 404 Not Found
value:
statusCode: 404
message: Language not found
error: Not Found
'500':
description: Internal server error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
examples:
error:
summary: 500 Internal Server Error
value:
statusCode: 500
message: Internal server error
error: Internal Server Error
security:
- bearer: []
components:
schemas:
Languages:
type: object
properties:
id:
type: string
example: lang_abc123
description: Signed language ID
required:
- id
ErrorResponse:
type: object
properties:
statusCode:
type: integer
example: 400
message:
oneOf:
- type: string
- type: array
items:
type: string
example: phone_number must be a valid E.164 phone number
error:
type: string
example: Bad Request
required:
- statusCode
- message
- error
securitySchemes:
bearer:
scheme: bearer
bearerFormat: JWT
type: http
````