oanor
Sign up free
Marketplace Pricing Features Sign in

API · /bcp47-api

BCP 47 Language Tags API

healthy 3,779 Subscribers

IETF BCP 47 language tags (locales) as an API, built on the IANA Language Subtag Registry — 9,200+ subtags (languages, scripts, regions, variants, extlangs and grandfathered tags). The headline /parse endpoint validates and decomposes any language tag (e.g. zh-Hant-TW → Chinese + Han Traditional script + Taiwan; en-Latn-US, de-CH-1996, i-klingon) into its labelled subtags, flags invalid or deprecated parts, and recognises pre-registered redundant/grandfathered tags. Look up an individual subtag (de → German, Hant → Han Traditional, 419 → Latin America), or search the registry by description. Ideal for internationalization (i18n), locale validation, content negotiation and language-aware apps.

#bcp47 #language-tags #locale #i18n #subtags #ietf
api.oanor.com/bcp47-api
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/bcp47-api/openapi.json
/api/bcp47-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
81 ms
Server probes · 24h
Subscribers
3,779
active
Total calls
244
last 7 days
status Full status page → · 16 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 10,000 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 10,000 calls/month
  • 2 req/sec
  • Parse + subtag + search
  • No credit card
Sign in to subscribe

Starter

€3.50 /month

  • 90,000 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 90k calls/month
  • 8 req/sec
  • Tag validation at scale
  • Email support
Sign in to subscribe

Pro

€11.00 /month

  • 450,000 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 450k calls/month
  • 20 req/sec
  • i18n / content negotiation
  • Priority support
Sign in to subscribe

Mega

€28.00 /month

  • 2,200,000 calls / month
  • 50 requests / second
  • Hard cap (429 above quota, no overage)
  • 2.2M calls/month
  • 50 req/sec
  • Localization platform
  • Dedicated SLA
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

Localized Names API

Get the localized display name of a code in any language — countries and regions, languages, currencies, scripts and calendars. Pass a code, a type and a locale and the name endpoint returns the right name: US as region in fr gives "États-Unis", de as language in fr gives "allemand", EUR as currency gives "Euro", and the same code reads correctly in German, Japanese, Arabic or any other locale. The list endpoint returns every code of a type localized and sorted in that locale's collation — ideal for building a country, language or currency dropdown in any language. Powered by the platform's full ICU data (Intl.DisplayNames) and computed locally with no network calls. Built for internationalised forms and pickers, multilingual UIs, localized reports and onboarding. A localized-names resolver — distinct from country reference data in English (countries), number and currency formatting (numberformat) and locale date formatting (datelocale). No upstream key, no cache.

api.oanor.com/displaynames-api

Relative Time & Locale Date API

Humanise timestamps and format dates for any locale and timezone using full ICU. The relative endpoint turns an instant into a localised relative phrase against now (or a given reference time) — "3 hours ago", "vor 3 Stunden", "in 2 days", "il y a 5 minutes" — automatically choosing the best unit from seconds to years. The format endpoint renders a localised date/time string (e.g. "mardi 2 juin 2026 à 15:30" or "2026年6月2日 22:30:00"), honouring the locale (BCP 47), a named IANA timezone, the chosen date and time styles (full/long/medium/short) and 12/24-hour preference, and returns a parts breakdown for custom displays. Pass dates as ISO 8601 or unix timestamps. Everything is computed locally with no network calls. Ideal for internationalised UIs, activity feeds, notifications, comments and dashboards. A relative-time and locale date formatter — distinct from current-time-in-a-timezone (time), the UTC parse/token toolkit (datetime) and number/currency formatting (numberformat). No upstream key, no cache.

api.oanor.com/datelocale-api

Number & Currency Formatter API

Format numbers for any locale using full ICU data — the correct way to display money, percentages and measurements per region. Pass a value and a style and the format endpoint returns the locale-correct string: decimal, currency (any ISO 4217 code, with the right symbol and grouping — e.g. 1.234.567,89 € in de-DE, $1,234,567.89 in en-US, ￥1,234,567 in ja-JP, and the Indian lakh grouping 12,34,567.89 in hi-IN), percent, or unit (e.g. 80 km/h). Control the locale (BCP 47), minimum/maximum fraction digits, grouping, sign display and notation (standard, scientific, engineering or compact like 1.2M). A parts endpoint returns the formatToParts breakdown (integer, group, decimal, fraction, currency symbol…) for building custom-styled displays. Everything is computed locally with no network calls. Ideal for internationalised UIs, invoices and receipts, dashboards and reports. A locale number/currency formatter — distinct from foreign-exchange rates (currency), number-to-words (numberwords) and the numeral-base converter (baseconvert). No upstream key, no cache.

api.oanor.com/numberformat-api

Text Segmentation API

Count and split text the way people actually read it, using Unicode-correct segmentation. The count endpoint returns the number of grapheme clusters — the real, user-perceived characters, so a family emoji counts as 1 (not 7) and an accented letter as 1 — alongside words, sentences, code points, UTF-16 code units (the naive string length that over-counts) and UTF-8 byte length. This is exactly what character-limit fields, tweet/SMS counters and validation need so the count agrees with what the user sees. The segment endpoint splits text into grapheme, word or sentence segments (word segments are flagged word-like versus punctuation and spaces) and is locale-aware, so Japanese, Chinese and Thai word boundaries come out right. Everything is computed locally with no network calls. A Unicode text segmenter — distinct from the Unicode codepoint database (unicode), the case/text-utilities toolkit (text) and string similarity (similarity). No upstream key, no cache.

api.oanor.com/segmenter-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for BCP 47 Language Tags API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call BCP 47 Language Tags API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for BCP 47 Language Tags API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does BCP 47 Language Tags API cost?
BCP 47 Language Tags API has a free tier with 100 calls / month. Paid plans start at €3.50 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is BCP 47 Language Tags API GDPR-compliant?
All requests to BCP 47 Language Tags API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Pick an endpoint from the list on the left to see its details and try it.

Code snippets

Sign up to get an API key, then call any path under your slug.

curl https://api.oanor.com/bcp47-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/bcp47-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/bcp47-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
    "https://api.oanor.com/bcp47-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

Sign in to rate.

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

Sign in to start a thread or reply.

Sign in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 This thread is locked — no new replies.

  • No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Sign in to open a support ticket.

Sign in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.