List tickets
List paginated ticket summaries with filters, sorting, and cursor pagination.
POST
List tickets
{} and applies the default pagination and sorting behavior.
Required access
Body
Whether to include the total matching record count. Set to
false for faster cursor syncs when you only need records and cursor.Ticket status filter. Use
all or omit the field to avoid status filtering. Supported view-style values include open, reopened, investigating, snoozed, waiting_on_customer, and closed.Comma-separated human agent or AI agent UUIDs. Use
current where the API request is associated with a user context. See Resource IDs.Comma-separated channel UUIDs. Find channel IDs in Settings > API Details > Channels. See Resource IDs.
Built-in or custom view code. Built-in values include
needs_attention, awaiting_reply, needs_first_human_reply, and mentions.Comma-separated team UUIDs. See Resource IDs.
Object mapping custom field IDs to filter values. For multiple accepted values on one field, pass a comma-separated string.
Date preset or explicit range. Supported values include
today, yesterday, last_7_days, last_30_days, start|end, start|, or a start-only ISO timestamp.Date field used with
date_range. Supported values are created_at, last_message_created_at, chat_escalated_at, closed_at, and updated_at.Field used for ordering and cursor generation. Supported values are
created_at, last_message_created_at, chat_escalated_at, closed_at, and updated_at.Response
Notes
- Use API client v2 credentials with
tickets:readscope and theticketsdataset grant. See API client v2. - Multi-value filters are comma-separated strings.
- Use
assigneewithassignee_typeto filter by human agents or AI agents.