Language API

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

name

English name

local_name

The language's own name for itself (日本語 for ja), null when unknown

script

ISO 15924 script code (Latn, Jpan, Arab)

direction

ltr or rtl

countries

ISO2 countries listing this language

Pass a code

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

Get the native name

English name, endonym, script, LTR or RTL.

Pair it with /country

Country responses already carry these codes.

225 languages.

Name, script, direction. Every plan.

159
with a native name: 15
right-to-left

Pass en, ja, or gsw and get back the language name, its own name for itself, the script it writes in, and whether it reads left-to-right or right-to-left. Both code lengths work: /language/en and /language/eng return the same thing. ISO 639 records.

/country/{code} already returns languages as these codes. Come here for the full record, native name and direction included.

RESPONSE

$ curl "https://api.parseapi.com/language/en" \
  -H "X-API-Key: YOUR_API_KEY"

// 200 · ~35ms US · ~97ms worldwide
{
  "language": "en",
  "iso3": "eng",
  "name": "English",
  "local_name": "English",
  "script": "Latn",
  "direction": "ltr",
  "countries": [
    "AG",
    "AI",
    "AS",
    "AU",
    "BB",
    // ... 86 more
  ]
}

Response fields

language: BCP 47 shortest code. ISO 639-1 when it exists (en), ISO 639-3 otherwise (gsw)
iso3: ISO 639-3 code
name: English name
local_name: The language's own name for itself (日本語 for ja), null when unknown
script: ISO 15924 script code (Latn, Jpan, Arab)
direction: ltr or rtl
countries: ISO2 countries listing this language

QUESTIONS

Which codes work?: ISO 639-1 or 639-3. Same record either way.
What comes back?: English name, endonym, script, and LTR or RTL.

SPEED

How long /language takes.

11ms

APAC

39ms

LatAm

10ms

101ms

See live status →

Coverage

Official language records.

Get started Docs