One request in.Six languages out.
No inbox, no waiting. Your systems talk to ours through the LanguageDesk API: a release is tagged, the strings are sent, the translations come back as a pull request. Follow one call from start to finish.
It starts with a commit.
A developer merges a feature. The build pipeline spots new and changed strings and posts a project to the API by itself — nobody has to remember to order translations.
- build
- test
- localize
Answered in milliseconds.
The API checks the request, creates a project and replies with its number before the pipeline has moved on. It is a real project, exactly like one opened by hand — your team can see it in LanguageDesk straight away.
The content type picks the service.
How much human goes in is agreed once, per kind of content. Changelogs: AI only. The interface: AI plus linguist review. Legal texts: full professional translation. After that, a request only has to say what it is.
"Changelog""App UI""Legal"Memory does the first pass.
Before any engine or linguist starts, every string is compared with your translation memory. Most of this release has been translated before — and is simply reused.
Translated while the build runs.
AI engines tuned on your memory and termbase translate all six languages in parallel. Placeholders, plurals and length limits are protected — and every string gets a confidence score.
checkout.pay_nowPay nowJetzt bezahlen
98cart.items_count{count} items in your cart{count} Artikel in Ihrem Warenkorb
97error.session_expiredYour session has expired.Ihre Sitzung ist abgelaufen.
96player.resumeResumeLebenslauf
58A human where it matters.
Confident strings pass straight through. The uncertain few go to a linguist who sees the screen they belong to. “Resume” on a video player is not a CV — a person spots that in a second.
player.resumeResumeLebenslauf
58Lebenslauf→Fortsetzen
Always know where it stands.
No status meetings, no “any news?” emails. Your pipeline asks the API and gets a straight answer: in progress, or completed, with a delivery date. It is the same status your team sees in LanguageDesk.
Merged before the release.
One more call returns the delivery files. The pipeline unpacks them, opens a pull request and runs the tests. Translations ship with the feature — and every approved string goes back into the memory.
- Tests passed
- Placeholders intact
- Merged
Your pipeline is one request away.
Tell us what your systems look like. We’ll show you the calls that connect them.