API connection Translation, in a single API call.
The tolingo API connection makes translation part of your software. An order goes out as a request, status and result come back automatically, with no order form and no copy-paste. Talk to us now about your options for an API key.
Four ISO certificationsTranslation partner for companies with high standards
- What it is: A REST interface your software uses to create, track and receive translation orders automatically.
- Who it's for: Developer teams and companies that want to build translation into their own applications, pipelines or workflows.
- How: Order by request, key authentication, status by webhook, result returned as localised content, as a specialist translation on request.
- The difference: No order form, no email traffic. Translation becomes a step in your code, coupled with translation memory and terminology.
From order form to function call
Translation becomes part of your software
A classic order means: export the file, upload it, wait for a quote, approve, download the result, feed it back in. For one-off projects that's fine. With ongoing needs it turns into daily work. The API replaces that with an API call your application triggers itself. As a technically minded translation agency, tolingo treats translation there as what it is in the AI era: a process that can be automated.
The manual order
Every translation is its own hand-worked task.
- Export the file and upload it by hand
- Wait for status updates by email
- Download the result and copy it back
- Start over with every new text
The automatic API call
Your application orders and receives on its own.
- Order by request, straight from your system
- Status by webhook, with no chasing
- Result comes back automatically as JSON
- Repeatable as often as you like, with no extra work
An order through the API
Three steps from the request to the finished text
Order by request
Your application sends the content, language pair and the quality level you want to the endpoint. Authentication runs through an API key, and the transfer is encrypted.
Translation runs
The order is processed: as machine translation, with post-editing, or as specialist translation to ISO 17100. Translation memory applies automatically.
Result comes back automatically
A webhook reports completion, and the result comes back to your application as a structured response. No login, no download, no manual step.
In day-to-day operation Once it's set up, it runs without your involvement: content goes out, translations come back. Translation becomes a service inside your architecture.
What teams use the API for
Wherever translation recurs
The API pays off as soon as translation comes up regularly. Typical uses:
New items and descriptions from your PIM or shop go into translation automatically, ideal for e-commerce with a large range.
String files from the build process. The API fits into CI/CD pipelines and ongoing software localisation along with technical documentation.
New pages and blog articles from your CMS trigger a website translation automatically as soon as they're published.
Help articles and reply templates from your helpdesk become multilingual as soon as they're created or changed.
Internal tools and automations, for example through Make or Zapier, trigger translation as one step among many. Common in the technology and software sector.
Portals and marketplaces that need content in many languages on an ongoing basis, without assigning a team to it.
Technology and security
Built so the connection holds up
The API is built on common standards: REST, key authentication, responses as JSON, status updates by webhook. You can connect from any common programming language. Recurring content benefits from the enterprise translation memory. Security is part of the architecture: tolingo works to ISO/IEC 27001, with encrypted transfer, processing on European servers and clearly governed access. On request, we sign an NDA before the first data exchange.
You don't have to integrate the API yourself. If you want the connection to a specific system, system integration takes that on. The API is the interface; the integration is the build into your tools. Our translations do not replace a technical acceptance test of your application.
Part of Technology & API
The API is the interface; three building blocks make it strong
The API does the transport. What runs through it, three further building blocks make better, cheaper and more consistent:
Builds the API into your specific systems: CMS, PIM, helpdesk or repository. The build that goes with the interface.
The store of already translated content. It applies automatically to API orders and lowers the cost.
Your terminology, settled. Every specialist term comes out the same in every language, through the API too.
The platform where API, memory and terminology come together as a finished solution.
Common questions about the API
Access, effort, quality, security
How do we get access to the API?
We set up access after a short kick-off call. You get an API key and the documentation for the endpoints. Get in touch, we'll clarify your use case and switch your access on.
Which programming languages are supported?
The API is a REST interface with JSON, so you can address it from any common language, such as Python, JavaScript, PHP, Java or C#. You need no special library; an HTTP client is enough.
Do we get raw machine translation or checked quality?
You choose the level per order: raw machine translation, post-editing to ISO 18587 or specialist translation to ISO 17100. The API governs the path; you govern the depth.
How does the API differ from system integration?
The API is the interface itself. System integration is the build of that interface into a specific system such as a CMS or PIM. If you develop in-house, you use the API directly. If you want a ready-made connection, you choose integration.
How secure is the data transfer?
tolingo is certified to ISO 27001. Transfer is encrypted, processing runs on European servers, and access goes through authenticated keys. With an NDA before the first exchange on request.
Technology & API
Want more than the interface alone?
API, translation memory, terminology and integration mesh together. The overview shows how the building blocks work as one.
Tell us what you want to connect.
Give us your use case and the volume you expect. We'll set up your API access and give you a clear read on effort and value.
Technical kick-off call · ISO 27001 · REST & JSON