Control the i18n process

from your command line

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.

Every new account comes with a 14-day trial period with the Business Plan active to try all the features before committing to a paid subscription, so you can test all of the integrations before you pay. You can also send us a message to request additional seven days if you need more time to test everything out!

You don’t need to enter any payment info at all to test the following integration options:

• Localazy API
• CLI
• Android and iOS SDK
• Manual file uploads
• Figma
• Strapi
• Storyblok
• Directus CMS
• Intercom
• Zapier
• … more coming!

Learn more about Localazy pricing options

Your projects can often contain multiple keys with the same content. Be it button labels across a large-scale information system, including keys on the backend and frontend or Android vs. iOS versions of your app. There are two ways to approach duplicate keys with Localazy.

The first option to consider when you have two or more projects that contain duplicities is to use the Connected Projects feature, which is available with the Professional plan. Connected Projects can help you by translating identical keys across multiple projects. This feature is great for a portfolio of projects sharing duplicate keys or Android and iOS versions of the same app. When enabled, Localazy distributes existing translations between connected projects and automatically decides whether the translation can be used right away or needs to go through review first.

For a robust duplicity management that can work with duplicities inside one project and across multiple projects as well, we recommend the Duplicity Linking feature, available with the Business plan. With duplicity linking, you can define one key as the source for all other keys with the same or similar content. The other keys are then marked as hidden and get their translation from the linked key.

Simply contact us and don’t hesitate ask! We are doing our best to keep the documentation up to date, but if you need help finding something and are sure you looked everywhere, please feel free to ask. You will most likely get a very quick reply and help us tremendously to improve the docs if the information is truly missing.

You can also join our Discussion Forum where you can meet and discuss any struggles or ideas with other Localazy users and our team members.

To fully automate your localization process and integrate uploads and downloads into your workflows, you can use either GitHub Actions or GitLab CI/CD.

Learn more about setting up Localazy with GitHub Actions in this guide on our blog: Automated Localization: GitHub Actions

Read more about using GitHub Actions with Localazy on our blog.

If you prefer using GitLab, you can see an example configuration in this article: Automated Localization: GitLab CI/CD

Localazy is also available as a Verified Step on the Bitrise platform. YOu can learn more about using Localazy with Bitrise here: Automated Localization: Bitrise.io

If you need help setting up your workflow, feel free to contact us.