Translation API

AI Translation endpoint is available for users on Professional and upper tiers. Each translation request consumes Localazy credits from your Localazy account balance. The number of credits used depends on the number of translated words.

You can use all of the Management endpoints absolutely for free. However, there are some limitations to prevent abuse.

Learn more about the limitations of Localazy API in the documentation.

After you sign up, you can obtain the tokens at https://localazy.com/developer/tokens

Project Token

• The project token gives you an access to a single project in Localazy.
• Each token is automatically granted a read and write access.
• Each project token has access to all availabe API endpoints.

Translation Token

• The translation token gives you access only to the AI Translation endpoint, with its context derived from the respective project in Localazy

Using translation software is the new normal for translation, but how can they assist in translating your app or web content? It usually happens through APIs. For understanding translation APIs is we must understand what an API is.

API stands for Application Programming Interface. Basically, by using an API, two applications can communicate with one another.

A translation API is an interface that lets you send text to a service and get translations back programmatically. Instead of copying strings into a translation tool manually, your code sends a request and receives translated content in the response. This is useful when you want to translate content on the fly, integrate translations into your build pipeline, or automate parts of your localization workflow.

Most translation APIs work as simple input/output endpoints. You send text in one language, pick a target language, and get the translation back. Services like Google Translate or DeepL offer this kind of API. It works well for quick translations, but it doesn’t know anything about your product, your terminology, or how you want things to sound.

Localazy Translation API #️⃣

Localazy now offers a translation endpoint as part of its existing API: POST /projects/{projectId}/ai.

It gives you access to Localazy AI and other machine translation engines directly from your code.

A few things that make it different from a generic translation API:

• You can translate multiple items in a single request, including plural forms.
• You can pass optional context along with your strings, so the translation engine understands what it’s translating and where it appears.
• And you can configure fallback engines, so if one provider doesn’t support your target language, the request still succeeds using an alternative.

Because the endpoint is tied to your Localazy project, translations can take advantage of your existing glossary and style guide. This means your API-driven translations stay consistent with everything else in your project.

Translations made through this endpoint consume credits from your account, the same credit system used across all Localazy services.

The Localazy API lets you interact with your localization projects programmatically. It covers two main areas: translating content with AI and managing your project data.

Translation #️⃣

The AI Translation endpoint lets you translate content directly through the API using Localazy AI. You send strings in your source language and get translations back in the target language, with your project’s glossary and style guide applied automatically.

You can translate multiple items in a single request, including plural forms, and pass additional context like key names, comments, and length limits to improve accuracy. If you need a safety net, you can set a fallback engine (like DeepL) so requests still succeed even if the primary engine can’t handle a specific language pair.

Each translation consumes credits from your account.

Project management #️⃣

The rest of the API is built for managing your localization workflow. You can:

• Import and export content in JSON format
• List and manage files, keys, and their translations
• Create, update, and delete glossary terms
• Upload screenshots and link them to specific keys for visual context
• Configure webhooks to get notified when translations are published, imports finish, or comments are added
• List projects, languages, and supported file formats

This means you can build custom integrations, automate repetitive tasks, or connect Localazy to internal tools without relying on the UI.

For example, you could set up a webhook that triggers your CI/CD pipeline whenever translations are published, or write a script that syncs glossary terms from an external terminology database.

The Localazy API gives you full programmatic control over your translations, from getting content translated to integrating it into your workflow.

Translate content directly #️⃣

The AI Translation endpoint lets you send strings and get translations back with your project’s glossary and style guide applied automatically. You can batch multiple items in one request, add context like key names or comments for better accuracy, and set fallback engines so requests don’t fail if a specific language pair isn’t available.

Fetch translations server-side #️⃣

You can pull translated content through the API as part of your server-side logic. This is useful for custom setups where you need to process or transform translations before they reach your users. For client-side delivery, Localazy offers a dedicated CDN that handles caching and global distribution for you.

Automate the workflow around it #️⃣

Import and export content, manage glossary terms, upload screenshots for visual context, and set up webhooks that notify your systems when translations are ready. This lets you connect Localazy to your CI/CD pipeline or internal tools so translations flow into your product without manual steps.

You can import content by making a POST request with your files in any of the supported formats, where each file should include a name, content type, and the actual content with key-value pairs for translations. The API will return an ID of the import batch that you can use for future operations.

Learn more here: Localazy Docs - API: Import

Yes, Localazy API has request limitations of 100 requests per minute and 10 requests per second. If you need higher throughput, especially for production environments, consider using Localazy CDN for content delivery.

Learn more about the Localazy API limits