Search cases by filter criteria to get matching case IDs, which can then be passed to the lookup endpoint for full details.
What this endpoint does
Searches cases and returns matching TaskIdentity IDs — this is step one of a two-step workflow. All filter parameters are optional; an empty body returns all accessible cases. Filters use AND logic: status (New, InProgress, Resolved, Dismissed), priority (Informational, Moderate, High), assignee (uhash or empty string for unassigned), created/modified date ranges. Control sort order with order_by (created or modified) and direction (asc or desc). To retrieve full case details, pass the returned IDs to Cases: Lookup Many.
Response data
Returns an array of TaskIdentity strings — IDs only, not case details. Paginated via cursor: read next_offset from the response and pass it as offset on the next request. The token is absent when no further pages exist. Pass the IDs to Cases: Lookup Many to get the actual case data.