GET /language/{code}

Language API

Pass en or ja. Get the name, script, and direction.

Try it

Example response/language/en
{
  "language": "en",
  "name": "English",
  "name_local": null,
  "script": "Latn",
  "direction": "ltr",
  ?deep=true
}

1M requests · $20/mo. Get started

What comes back.

name

English name

name_local

The language's own name for itself (日本語 for ja), null when absent or identical to name

script

ISO 15924 script code (Latn, Jpan, Arab)

direction

ltr or rtl

deep.countries

ISO2 countries listing this language

1

Pass a code

ISO 639-1 or 639-3. Same record either way.

2

Get the native name

English name, endonym, script, LTR or RTL.

3

Pair it with /country

Country responses already carry these codes.

Make your first request.

One key works across the APIs. Copy a request in your language and get JSON back.

curl "https://api.parseapi.com/language/ja" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Parse-Version: 2.0.0"
// Example response · 200
{
  "language": "ja",
  "name": "Japanese",
  "name_local": "日本語",
  "script": "Jpan",
  "direction": "ltr"
}

API referenceSDKsKeys and authentication

Every response field

Response fields

languagestring
BCP 47 shortest code. ISO 639-1 when it exists (en), ISO 639-3 otherwise (gsw)
namestring or null
English name
name_localstring or null
The language's own name for itself (日本語 for ja), null when absent or identical to name
scriptstring or null
ISO 15924 script code (Latn, Jpan, Arab)
directionstring
ltr or rtl

Deep fields

deep.iso3string or null
ISO 639-3 code
deep.countriesarray
ISO2 countries listing this language

QUESTIONS

Which codes work?
ISO 639-1 or 639-3. Same record either way.
What comes back?
Language code, English name, native name, script, and direction. Add deep=true for the three-letter code and associated countries, included on every plan.