Getting started

Localization? Nothing simpler than that!

Follow these three quick steps:

1. Register a free account.
2. In your account dashboard go to API Tokens and create a new token.
3. Add one of the following commands to your extraction process:

XLIFF

curl https://api.doloc.io -H "Authorization: Bearer $API_TOKEN" --data-binary "@input.xlf" -o output.xlf

See XLIFF 1.2 and XLIFF 2.0 format guide for more info!

JSON

curl https://api.doloc.io -H "Authorization: Bearer $API_TOKEN" -F source="@source.en.json" -F target="@target.de.json" -o result.de.json 

See our JSON format guide for more info!

Further Formats

Other formats are also supported, such as:

• Android XML Resources for Android apps,
• Properties for Java applications,
• ARB for Flutter apps,

This will automatically upload the translation file(s) and translate all targets! You choose, if you want your input file be overwritten by the output file or not!

Windows Users: Did you know curl is installed on all windows 10/11 versions? For PowerShell you might need to replace curl with curl.exe!

How to integrate

You can add the above process to your CI/CD pipeline, but it’s even better to run it earlier: Whenever a developer updated any text, simply run the command to keep translations up to date. This keeps translations current, helps spot missing entries early (for example, during PR review), and is quick to set up.

For a more detailed discussion on when to run doloc, see our guide on When to Run doloc?.

Further Reading

• File Format Guides – Supported file types and how to prepare/submit each for translation.
• Integration Guides – Step-by-step setup for Angular, React Intl / FormatJS, Android, Flutter and more.
• Options – How to pass configuration parameters to the translation endpoint.
• Examples – Complete input/output samples for supported file formats.
• When to Run doloc – Best practices on integrating doloc into your development cycle.