Translation Workflows Built for Developer Teams
Integrate translation directly into your development pipeline. REST API, CI/CD integration, string file translation, glossary enforcement, and batch operations — built for engineers who automate everything.
How Developer Workflows Work
Get Your API Key
Sign up for a free account and generate an API key from your dashboard. Your key works immediately — no approval process.
Add Translation to Your Pipeline
Add an API call to your CI/CD pipeline. Send source strings in JSON, receive translations in the same structure.
Configure Glossary & Engine
Set your preferred engine (DeepL, Google, Microsoft, GPT, Gemini) and attach a glossary for product-specific terminology.
Automate Releases
Translated files are ready to commit. Ship multilingual releases automatically with every build.
Features for Developer Teams
A translation API designed for automation — not manual workflows. Ship multilingual software faster.
REST API with JSON Responses
Simple REST endpoints that accept and return JSON. Translate text, documents, and string files programmatically with a single HTTP call.
CI/CD Pipeline Integration
Add a translation step to GitHub Actions, GitLab CI, Jenkins, or any pipeline. Automate i18n as part of your build and deploy process.
String File Translation
Upload JSON, YAML, PO/POT, XLIFF, CSV, and ARB files. Keys are preserved, only values are translated — ready to drop back into your project.
Glossary API
Create and manage glossaries programmatically. Enforce consistent terminology across automated translation workflows.
Batch Operations
Translate multiple strings or files in a single API call. Reduce round trips and speed up large localization jobs.
Webhook Notifications
Receive webhooks when long-running translations complete. No polling required — your pipeline continues automatically.
Developer Use Cases
From React i18n to mobile app localization — automate translation for any development stack.
React & Angular i18n
Translate JSON message files for react-intl, i18next, Angular i18n, or ngx-translate. Keys stay intact, values get translated.
Mobile App Localization
Translate iOS Localizable.strings, Android strings.xml, and Flutter ARB files. Ship multilingual mobile apps with every release.
Game String Translation
Localize in-game dialogue, UI labels, achievement descriptions, and store listings for global game launches.
API Response Localization
Translate error messages, notifications, and user-facing API responses on the fly for multilingual SaaS products.
CLI Tool Translation
Localize help text, error messages, and prompts for command-line tools distributed to international developer communities.
Documentation Pipelines
Integrate translation into your docs-as-code workflow. Translate Markdown, MDX, and RST files as part of your documentation build.
Frequently Asked Questions
What are the API rate limits?
Free tier: 60 requests per minute. Pro plans: 300 requests per minute. Enterprise: 600+ RPM with custom limits. All plans include retry-friendly 429 responses with Retry-After headers.
What string file formats does the API support?
The API supports JSON, YAML, PO/POT, XLIFF, CSV, ARB (Flutter), and plain text. File structure and keys are preserved — only translatable string values are processed.
Are there SDKs or client libraries available?
The REST API uses standard HTTP with JSON payloads, so it works with any HTTP client in any language. Use fetch, axios, requests, or curl — no proprietary SDK needed.
How do I integrate with GitHub Actions?
Add a step that calls the translation API with curl or any HTTP client. Pass your API key as a secret, send your i18n files, and commit the translated output. Example workflows are available in our API documentation.
Can I use different engines for different languages?
Yes. Specify the engine per request. For example, use DeepL for European languages and Google for Asian languages. You can also use Multi Translate Pro to compare all five engines and pick the best per language.
How does the glossary API work?
Create glossaries via the API with source and target term pairs for each language. Attach a glossary ID to translation requests, and the engine will enforce your terminology automatically.
What does API access cost?
Free accounts include 3,000 credits and API access. Paid plans start at $9.99/month for 100,000 credits. All plans include full API access — there is no separate API pricing tier.
How do I handle translation for large files?
For files over 10,000 characters, use the document translation endpoint which processes asynchronously. You receive a job ID and can poll for completion or configure a webhook to be notified when the translation is ready.
Integrate Translation Into Your Workflow
Add AI-powered translation to your CI/CD pipeline. REST API, string file support, and glossary enforcement — free to start.