Skip to main content

​
Docs languages and translations

This documentation site ships in six languages — English (source), Turkish, Arabic, German, French, and Spanish — and serves every locale from one English corpus. This page explains exactly what that means.

​
What is translated today

Six locale variants exist. Per variant, three anchor pages are translated natively — Introduction, Quickstart, and Authentication. Everything else — endpoint references, channel guides, compliance matrices, SDK docs, concepts — renders the English page. You always see the complete corpus, in English; nothing is machine-translated on the fly or silently filtered per locale.

​
Why one corpus

the documentation tracks the product API one-to-one — endpoint references, request fields, response shapes, and error codes are written and reviewed in English. Routing pages through per-locale translation before they ship would delay updates and risk mistranslating the exact field names you send in a request, so one correct version ships in English.

​
Per-locale guarantees

  • The same archive — a Turkish or Arabic account sees exactly the pages and links an English account sees; no content is filtered by locale.
  • English-only titles — page titles (the string the page and search put in front of a reader) are swept for non-Latin scripts, so an English reader never meets e.g. an Arabic phrase embedded mid-sentence on the English corpus.

​
What is not affected

The product dashboard localises its chrome fully (menus, buttons, labels) and the product changelog is a separate published surface with its own language policy — only this docs site follows the English-corpus rule above.

​
What to expect next

Translated copies of the wider corpus are being seeded on a rolling basis; when a locale’s coverage is ready that locale flips to its translated docs as one coherent rollout, announced on the product changelog.