Enable Side Conversations in your Zendesk Admin Center under Objects & Rules before making API calls — the endpoints return errors if the feature is not activated.
Create a side conversation on a parent ticket with POST /api/v2/tickets/{ticket_id}/side_conversations, supplying 'message' (with 'subject', 'body', and 'to' recipients) and optionally 'type' (email or Slack).
List all side conversations on a ticket with GET /api/v2/tickets/{ticket_id}/side_conversations.
Retrieve the full message thread for a specific side conversation with GET /api/v2/tickets/{ticket_id}/side_conversations/{side_conversation_id}/events.
Reply to an existing side conversation with POST /api/v2/tickets/{ticket_id}/side_conversations/{side_conversation_id}/reply, supplying the message body and any additional recipients.
Subscribe to side conversation events by registering a webhook in Admin Center (Zendesk does not expose a dedicated side-conversation webhook API endpoint — use the standard webhook + trigger approach filtered on side_conversation event types).
Known gotchas
Side Conversations are a Zendesk Suite feature — they are not available on legacy Support-only plans; confirm your plan before building integrations.
Slack-type side conversations require the Zendesk for Slack integration to be configured and the target Slack workspace connected; email type works without additional setup.
The 'to' field in the message payload expects an array of participant objects with 'email' or 'slack_workspace_id'/'slack_channel_id' — mixing types in a single request will cause a validation error.
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