Translating a UI string in isolation is how you get a button labelled with the wrong sense of a word — "Post" as mail rather than publish. Telling the platform which keys sit next to each other gives the translation engine the surrounding context a human translator would have had. It is unglamorous and it is the single biggest quality lever here. Note also that their destructive tools say so in their own descriptions and ask the assistant to confirm first — the warning is delivered where it can actually take effect.
Tolgee is a localisation platform. Its endpoint covers the day-to-day work: keys, languages, namespaces, and machine translation as a job you poll.
- Keys — list, search by name or translation text, create with translations and tags, get, update, delete
- Languages and namespaces, plus per-language translation progress statistics
- Machine translation started as a batch job, with status polling
- store_big_meta — record how keys relate so translations of neighbouring keys become context for the machine translation
- Branches — list, create by forking, delete, on projects that have them
- Projects — list and create, the latter needing an account-wide token
A project API key or a personal access token as a header. Self-hosted instances expose the same path on your own domain. Their suggested first move is a read-only call to confirm the connection.
Paste a URL with a key — add the endpoint to your client