Localazy translation engine API is easy to configure.
Follow our documentation to get started and POST your content for translation now.
Use Localazy API for free to automate your i18n and translation efforts.
Continuously translate your content and GET your translations precisely when you need them.
You can use the API 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 token at https://localazy.com/developer/tokens
The project token is automatically permitted to read and write to the project.
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 works as a software interface that developers can use to add machine translation capabilities to their products or programmatically translate texts and content that their product displays in localized versions.
Localazy provides a Translation API as one way of integrating of software translation projects.
Localazy API can be used to fetch up-to-date translated content, modify it or upload new content for translation. You can also manipulate the source keys in the project, manage screenshots, duplicities, webhooks and glossary terms.
Localazy Translation API endpoints allow you to:
Some use-cases where API is applicable:
Learn more about Localazy API endpoints in the documentation.
With Localazy API, you have great flexibility of implementation.
For example, when you want to provide up-to-date translations without having to release a new version of your application, you can fetch everything through API and only fall back to static files in case of an error or as a fallback until the files are properly fetched, or you can skip using the static files whatsoever and use API only.
Basically all you have to do is: