list_side_conversations
Read-onlyIdempotent
Fetch side conversations attached to a ticket to surface parallel email or Slack threads from the Collaboration add-on.
Instructions
List side conversations (Collaboration add-on) attached to a ticket as paginated skeletons. Plan-gated, on instances without the Collaboration add-on the call degrades to a structured upstream_error envelope with the underlying http_status, not a thrown failure. Also scope-gated (config_plus_audits or full). Use to surface the parallel email/Slack thread on a ticket; for the main public conversation use get_ticket_comments.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max items to return. Default 100. The full corpus is fetched and cached server-side; this only limits what the response carries. | |
| cursor | No | Opaque pagination token from a previous response. Slices the next page from the cached corpus. Stale cursors (older than the cache TTL) auto-reset to offset 0 and set cursor_invalidated: true. | |
| fields | No | Whitelist of field names. Overrides the default projection. Use to opt into extra fields (e.g. ["id","title","active","position","category_id","updated_at"]) without going fully verbose. | |
| filter | No | Structured filter applied to the cached corpus before slicing. Supported keys: active (bool), category_id (number/string), title_contains (string, case-insensitive), updated_since (ISO timestamp). Unsupported keys are ignored with a note in the response. | |
| refresh | No | Bypass cache and re-fetch from Zendesk | |
| verbose | No | Return full side-conversation objects instead of the thin projection | |
| instance | No | Override the sticky instance for this call | |
| ticket_id | Yes | Ticket ID |