list_custom_statuses
Read-onlyIdempotent
Retrieve custom ticket statuses from Zendesk, with optional filtering by active state, category, or title, and pagination support.
Instructions
Returns custom ticket statuses as paginated skeletons (id, status_category, agent_label, active, default, updated_at). Default limit: 100; pass cursor, fields, filter, or verbose: true. Custom-status lists are tiny (handful of entries), so straight enumeration is fine. For deeper hygiene checks (which rules reference deactivated statuses, etc.) trace via find_triggers_by_field with field: "status".
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 custom-status objects instead of the thin projection | |
| instance | No | Override the sticky instance for this call |