submit a Salesforce Knowledge article for translation and mark the translated version complete via REST
domain: salesforce.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
Salesforce Bulk API 2.0 limits — the full failure-mode walkthrough related to salesforce.com, checked against official docs, with linked verified routes.
Steps
Use the Knowledge REST APIs (Knowledge__kav) to identify the source article version to translate
Call the Submit an Article for Translation endpoint to queue the article version for translation into target languages
Have translators complete the translated content outside or alongside Salesforce
Call Set a Translated Article Version to Complete once the translated content is ready to move out of draft
Use Unpublish the Online Version of a Translated Article if a translated version needs to be pulled from publication
Verify the translated Knowledge Article Version via the Connect REST API to confirm status and locale
Known gotchas
Submitting for translation and marking a translation complete are distinct API calls — completing a translation doesn't automatically publish it online
Article version and translation state are exposed through different endpoint families (Knowledge Management REST vs. Connect REST) — reconciling full status requires checking both
Unpublishing a translated version only affects that locale's online visibility, not the source article or other locales
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?