Skip to main content
Use hyperlocalise smartling download translations --retrieval-type published to request published translations from Smartling. Specify the retrieval type explicitly so the intended export is visible in scripts and CI.

​
Before you start

Install Hyperlocalise, then set SMARTLING_USER_IDENTIFIER and SMARTLING_USER_SECRET for a credential with project access. This workflow expects source files and published translations already in Smartling. It does not start a translation job. Replace the project ID and inspect the available files and locale IDs:
Use the exact file URI returned by files list and an enabled target locale. --uri-mask is a substring filter for listing or multi-file downloads, not an alternative to an exact --file-uri.

​
Download one published locale

Review locales/fr-FR.json and check that required strings are present. Published retrieval does not prove the whole file is translated. Add --force if you intend to overwrite an existing output file.

​
Download a set of files

Use --all instead of --file-uri and provide a directory:
For URI locales/en.json, the exported path is smartling-export/locales/en_fr-FR.json. Add --uri-mask locales/ to limit the listed files. Downloads run sequentially and stop on the first error; inspect partial output before retrying. An empty file list produces an error. Do not use %locale% or stdout (-) with --all. With a single file and several --target-locale flags, use %locale% in the output filename instead.

​
If the export is missing content

Check file status, enabled locales, and publication state in Smartling. The pending, published, and pseudo retrieval types serve different purposes; changing to pending is not a substitute for completing your release workflow. See Smartling CLI workflows for upload behavior and credential differences from the official CLI, or all TMS integrations.