Configure MT/LLM fallback behavior within a Smartling workflow and drive it via the Jobs 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
Set up an MT or LLM Profile in Smartling and assign it to the relevant workflow step (this configuration currently lives in the Smartling dashboard, not a dedicated API resource)
Optionally define an Alternate MT Profile to translate a string if the primary MT/LLM profile fails (e.g., unsupported language, tag/placeholder mismatch)
Define a Fallback Method to automatically move strings that fail MT after repeated errors to a different workflow step (e.g., a human-translation queue)
Use the Jobs API to create the job, add content, and authorize it so strings actually flow into the MT-enabled workflow step
Poll job/file status via the API to detect strings that were rerouted to the fallback step, and alert on unexpectedly high fallback rates
Known gotchas
MT/LLM profile and fallback configuration is primarily a workflow-step setting made in the Smartling dashboard; the Jobs/Files API drives content through the workflow but does not itself configure the MT fallback rules
Repeated validation failures (e.g., 3 failures within a short window) trigger the fallback method automatically — a systemic placeholder/tag issue in source content can silently push large amounts of content to human queues and inflate cost
Job authorization is a separate explicit step from job creation; forgetting to authorize a job leaves added content sitting unrouted
Give your agent this knowledge — and 18,200+ more routes
One MCP install gives any agent live access to the full route map across 6,000+ 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?