Identify the section ID where the article will live: GET /api/v2/help_center/sections to list sections with their IDs and category associations.
POST to /api/v2/help_center/{locale}/sections/{section_id}/articles with a body under 'article' containing 'title', 'body' (HTML string), 'locale', and optionally 'label_names' and 'user_segment_id'.
The article is created in 'draft' status by default; to publish it, PATCH /api/v2/help_center/articles/{article_id} with 'draft': false.
Add translations for additional locales by POST to /api/v2/help_center/articles/{article_id}/translations with 'locale', 'title', and 'body'.
Update an existing article's body with PUT /api/v2/help_center/articles/{article_id}/translations/{locale} containing the updated 'title' and 'body'.
Delete an article with DELETE /api/v2/help_center/articles/{article_id}; this is permanent — consider archiving (setting 'draft': true) instead for content that may be needed later.
Known gotchas
Help Center must be activated in the Zendesk account before the Guide API is accessible — otherwise all endpoints return 403 Forbidden.
Article body must be valid HTML; Zendesk sanitizes dangerous tags (script, iframe) server-side, which may silently alter your content — validate the returned body against your input.
User segment restrictions on articles affect visibility for end users but not for API reads using agent credentials — test article visibility from a non-agent session before considering access control correct.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp