Docs

Documentation

One endpoint does the work. The rest of these pages exist so you never have to guess.

Getting started

Quickstart

Create a key, send your first translation request and read the response — the whole loop in under five minutes, with no SDK to install.
Authentication

How to send your API key, which two header formats are accepted, how key modes work and how to rotate a key without dropping a single request.
Migrating from DeepL

Point your existing client at vizvuz — the parameters, headers and response shape match, so a migration is usually a base URL and a key.
Client snippets

Copy-paste clients for PHP, JavaScript, Python, Go and the shell — small enough to read, with retries and error handling already in place.

Translate text

The full reference for POST /v1/translate — every parameter, the response shape, the headers we return and the limits that apply per plan.
Languages

The 36 source languages and 38 target languages, how regional variants are handled, and how to fetch the authoritative list from the API itself.
Usage and quota

Read your character count, limit, overage and prepaid balance from the API, and learn how reservations, caps and settlement actually work.
Glossaries

Force specific terms to be translated your way — create, inspect and delete glossaries, and attach one to a translation request.

Formality

Choose formal or informal address with one parameter, see which of the 36 languages support it, and how the "prefer" variants avoid errors.
Tag handling

Translate HTML and XML without breaking the markup — which nodes are translated, which are left alone, and how to keep placeholders intact.

Errors

Every error the API can return, in RFC 9457 problem+json, with the stable code, the HTTP status and the action that actually resolves each one.
Rate limits

Requests per second per plan, the headers that report your budget, how the sliding window works and how to size concurrency so you never see a 429.