Supported languages
API · /translate-api
Translation API
Translate text between 40+ languages with a confidence score and alternative suggestions. Simple GET interface, no model hosting — ideal for localising content, chat messages, product data and user-generated text.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 493 ms
- Server probes · 24h
- Subscribers
- 4,407
- active
- Total calls
- 40
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 2,500 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 2,500 translations/mo at 2 rps
- 40+ languages, single GET endpoint
- Confidence score included
- No credit card
Basic
€11.00 /month
- 40,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 40,000 translations/mo at 8 rps
- Alternative-suggestion field unlocked
- Commercial use allowed
- Email support
Pro
€39.00 /month
- 200,000 calls / month
- 25 requests / second
- Hard cap (429 above quota, no overage)
- 200,000 translations/mo at 25 rps
- Batch (multi-text) requests
- Auto language detection
- Priority email support
Mega
€109.00 /month
- 750,000 calls / month
- 60 requests / second
- Hard cap (429 above quota, no overage)
- 750,000 translations/mo at 60 rps
- 99.9% uptime SLA
- Highest-priority queue
- Dedicated support contact
Built by
Related APIs
Other APIs with overlapping tags.
Example Sentences API
Real example sentences with human translations as an API — powered by Tatoeba, the large collaborative corpus of millions of sentences in hundreds of languages, each linked to translations contributed and reviewed by real people (not machine translation). Search for sentences containing a word or phrase in one language and get how they are actually translated into another — perfect for seeing a word "in the wild", building vocabulary and flashcards, or as a human-quality translation aid. Look up any sentence by id to get its full set of translations. From "good morning" in English to its German, French, Spanish, Japanese or Mandarin equivalents, across ISO-639-3 languages, it is ideal for language-learning, vocabulary, flashcard, dictionary-companion and linguistics applications. A human-translated example-sentence corpus — distinct from dictionaries (definitions), machine translation and word APIs. Open data from Tatoeba (CC-BY 2.0 FR / CC0).
api.oanor.com/tatoeba-api
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
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
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
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Translation API?
What's the rate limit for Translation API?
How much does Translation API cost?
Can I cancel my subscription anytime?
Is Translation API GDPR-compliant?
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/translate-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/translate-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/translate-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/translate-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 inNew thread
·
-
Provider answer
🔒 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 inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.