oanor
Sign up free
Marketplace Pricing Features Sign in

API · /datelocale-api

Relative Time & Locale Date API

healthy 3,530 Subscribers

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.

#relative-time #date-format #i18n #locale #timezone #developer-tools
api.oanor.com/datelocale-api
Get an API key Try in playground → Contact provider

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

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

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

Relative Time & Locale Date API — live data on the oanor API marketplace

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
76 ms
Server probes · 24h
Subscribers
3,530
active
Total calls
60
last 7 days
status Full status page → · 12 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 2,060 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 2,060 calls/month
  • 2 req/sec
  • Relative + locale format
  • No credit card
Sign in to subscribe

Starter

€6.05 /month

  • 39,000 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 39k calls/month
  • 8 req/sec
  • Full ICU locales + timezones
  • Email support
Sign in to subscribe

Pro

€20.00 /month

  • 208,000 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 208k calls/month
  • 20 req/sec
  • i18n feeds & UI pipelines
  • Priority support
Sign in to subscribe

Mega

€52.20 /month

  • 800,000 calls / month
  • 50 requests / second
  • Hard cap (429 above quota, no overage)
  • 800k calls/month
  • 50 req/sec
  • Global-app scale
  • Dedicated SLA
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

Writing Systems (ISO 15924) API — oanor API marketplace

Writing Systems (ISO 15924) API

The ISO 15924 register of writing systems — the script codes used by Unicode, BCP-47 and CLDR — served from memory (no key). Every script carries its 4-letter code (e.g. Latn, Arab, Hani), numeric code, English and French names, the Unicode property value alias, the Unicode version it was added in and its date. Look a script up by code or numeric, search by code or name, or list the whole register. 226 scripts. Ideal for internationalization, locale and font tooling, BCP-47 tag validation and text-rendering pipelines.

api.oanor.com/scripts-api

 Content Negotiation API — oanor API marketplace

Content Negotiation API

HTTP content negotiation as an API. The parse endpoint reads an Accept, Accept-Language, Accept-Encoding or Accept-Charset header — with quality (q) values and parameters — into a clean list ranked by the client's preference. The negotiate endpoint takes that header plus the list of values your server can actually serve and returns the single best match, along with the full ranked result and the entry that matched each candidate. It applies the correct rules for each kind: media-type type and subtype wildcards (text/*, */*), RFC 4647 language-range matching (a request for en matches your en-US, and en-US falls back to en), and exact matching with a * wildcard for encodings and charsets — and a q=0 entry correctly rejects a value. Everything runs locally and deterministically, so it is instant and private. Ideal for i18n middleware and locale selection, API versioning by media type, response-format and compression selection, CDNs, proxies and edge functions. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This negotiates HTTP headers; to validate or decompose a single BCP-47 language tag use a BCP-47 API.

api.oanor.com/negotiate-api

 Punycode / IDN API — oanor API marketplace

Punycode / IDN API

Convert internationalized domain names (IDNs) between their human-readable Unicode form and the ASCII Punycode form (xn--…) that DNS actually uses. Encode a Unicode domain like münchen.de or 例え.jp (or even an emoji label like ☕.example) to ASCII, decode an xn-- domain back to Unicode, and convert a whole URL's host in either direction. Handles accents, non-Latin scripts and emoji. Useful for IDN domain handling, email and URL validation, DNS tooling, and spotting homograph / look-alike domains. Pure local IDNA conversion — no key, no third-party service, instant. Live. 4 endpoints. Distinct from Public-Suffix-List domain parsing and from generic text encoders.

api.oanor.com/punycode-api

 Text Segmentation API — oanor API marketplace

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 Relative Time & Locale Date API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Relative Time & Locale Date API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Relative Time & Locale Date 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 Relative Time & Locale Date API cost?
Relative Time & Locale Date API has a free tier with 100 calls / month. Paid plans start at €6.05 / 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 Relative Time & Locale Date API GDPR-compliant?
All requests to Relative Time & Locale Date 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/datelocale-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/datelocale-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/datelocale-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/datelocale-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.