Search Tickets
Search tickets with filters. Supports filtering by team, assignment, status, escalation level, time range, external ticket key, and parent_ticket_ids (all children of the given tickets — e.g. every task of a journey — matching the parent_ticket_id field on the ticket payload).
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Optional. Filter to specific teams. If not provided, searches all accessible teams.
Optional. Only return tickets assigned to any of these users.
Optional. Only return tickets requested by any of these users.
Optional. Filter by status IDs. Returns tickets matching ANY of the specified statuses.
Optional. Filter by escalation levels. Returns tickets matching ANY of the specified levels.
AI, HUMAN A timestamp in RFC 3339 format (e.g., "2025-01-15T01:30:15Z").
"2025-01-15T01:30:15.000Z"
A timestamp in RFC 3339 format (e.g., "2025-01-15T01:30:15Z").
"2025-01-15T01:30:15.000Z"
Maximum number of results to return. Default is 1000, maximum is 5000.
Token for pagination. Leave empty for the first request.
Optional. Only return tickets linked to any of these external tickets. Matches either the human-readable key (e.g. "GMD-29" for Jira) or the internal composite external ticket id. Case-sensitive. This is the single-request alternative to listing tickets and calling ListTicketExternalTickets per ticket.
Optional. Only return tickets whose parent is any of these tickets — the same relationship the response exposes as parent_ticket_id. For a journey ticket this returns its tasks in one request (and for a task, its subtasks), replacing per-ticket child lookups.
Optional. Only return tickets with any of these ticket numbers — the numeric half of the human-readable identifier ("5" for "DEV-5"). Numbers are unique only WITHIN a team, so combine this with team_ids; without it the search spans every accessible team and can return one ticket per team for the same number.

