Upload source files and download completed translations for a job with the Smartling Files API
domain: api-reference.smartling.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate and obtain a bearer token via the auth endpoint using your project's API credentials
POST the source file to the Files API upload endpoint, specifying fileUri, fileType, and target locale IDs to associate it with a job
Add the uploaded file to a translation job (or create the job first, then add file content) via the Jobs API so it enters the configured workflow
Poll file/job status endpoints to track progress through workflow steps before assuming translations are complete
Download completed translations per locale via the Files API's downloadFile (or downloadAllTranslations) endpoint once the job status indicates delivery
Known gotchas
A file must belong to a job (and the job must be authorized) before its strings move through workflow steps — uploading a file alone does not start translation
fileUri acts as the stable identifier for a file across re-uploads; changing it creates a new file rather than updating the existing one, fragmenting translation memory linkage
Downloading before a locale's workflow reaches the final step can return partially machine-translated or untranslated placeholder content depending on job configuration
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?