Localisation? Nothing simpler than that!

Just register, create an api token and add the following command into 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!

Android XML Resources

curl https://api.doloc.io -H "Authorization: Bearer $API_TOKEN" -F source="@res/values/strings.xml" -F target="@res/values-fr/strings.xml" -o res/values-fr/strings.xml 

See our Android XML Resources format guide for more info!

This will automatically upload the XLIFF, JSON or Android XML Resources 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 certainly integrate the above process into your CI/CD pipeline, but we recommend adopting it even earlier in your workflow. Whenever a developer updates any text, they should run the command to regenerate translations — often alongside extracting new texts to avoid additional overhead. This approach keeps translations current and helps you spot missing entries early on, for instance during a PR review. Plus, setting it up is straightforward and takes only a few minutes.

Further Reading