Product · Developer API
Localization that ships with your code
Treat translations like the rest of your stack: a REST API keyed by locale, namespace, and key; a universal JavaScript SDK; or an edge proxy that serves your live site translated. Pick the integration depth that fits.
REST i18n API
Strings in, strings out, no ceremony
Read and write translations by locale, namespace, and key. Sync runs asynchronously with batching, retries, and a dead-letter queue: a failed job is a queue entry, not a lost string.
ICU MessageFormat is parsed properly: plurals, selects, and nested messages survive translation with their structure intact, and a dedicated QA detector flags any malformed ICU message before it ships.
GET /translations/{locale}/{namespace}
POST /sync/batch # async, batched, with retry + DLQ
# keys live under locale / namespace / keyJavaScript SDK
One client, every runtime
The SDK wraps the API for Node, browsers, and React: cache-first with background sync and pluggable persistent storage, so your app renders from cache while updates land quietly behind it.
A types CLI generates TypeScript definitions live from your project: keys and ICU parameters become compile-time errors, and watch mode keeps them current as translators add strings. Rich inline content survives too: the React Trans component round-trips JSX through translation without flattening it to a string.
- Node & browser
- React bindings
- Cache-first + background sync
- Live-generated TypeScript types
- Styled translations
Edge proxy
Translate a live site without touching its code
Point the edge proxy at your site and serve translated pages to visitors from the CDN edge, or use a one-tag JS snippet, or the raw API. The proxy is built to recognise common platforms and apply the right preset.
Behind every mode sits the same platform: your TM, your terminology, the same QA.
- Runs at the CDN edge
- JS snippet
- API mode
Continuous localization
Projects that never finish, by design
Continuous-localization projects treat translation as an ongoing feed, not a one-off job: strings sync in as your product changes, and the same TM, terminology, QA, and human workflow apply to every increment.
Each project carries its own integration keys, which you can create, toggle, and revoke independently: no shared passwords, no embedded user accounts, and a compromised key never has more reach than its one project.
- Continuous projects
- Per-project integration keys
- Create · toggle · revoke
Wire it into your pipeline
Join the waitlist and we’ll tell you the day API keys open.