Publish and version a knowledge base article via the Zendesk Guide Help Center API and manage article translation locales
domain: developer.zendesk.com/api-reference/help_center · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with a Zendesk API token (email/token scheme) against https://{subdomain}.zendesk.com/api/v2
GET /api/v2/help_center/categories and /api/v2/help_center/sections to identify the target section ID where the article should be published
POST /api/v2/help_center/en-us/articles with section_id, title, body (HTML), locale, and draft:false to create and publish the article in the default locale
POST /api/v2/help_center/articles/{articleId}/translations with locale (e.g., fr, de) and the translated title and body to add alternate language versions
PUT /api/v2/help_center/en-us/articles/{articleId} to update the article body — this creates a new draft version; set draft:false to publish immediately
GET /api/v2/help_center/articles/{articleId}/subscriptions to list agents or end-users subscribed to change notifications for the article
Known gotchas
The locale code must be included in the API path (e.g., /en-us/articles) and must match a locale enabled in your Help Center settings — an unsupported locale in the path returns 404, not a validation error
Article body must be valid HTML; Zendesk strips disallowed tags server-side without warning — embedded scripts, iframes, and certain style attributes are removed silently, which can corrupt formatting on publish
Articles with user_segment_id restrictions (visible only to signed-in users or specific segments) return 403 when accessed by end-user tokens — test article retrieval with both admin and end-user credentials when building deflection flows
Give your agent this knowledge — and 15,600+ 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?