List hydrated cases with threat events
Returns cases scoped to the caller’s domain. Each case includes the full
threat event objects referenced by event_ids, so external systems can
process a case without making a second /threats lookup.
For polling integrations, use created_after with an ISO 8601 timestamp
to query cases created within a specific time window, for example:
GET /cases?created_after=2026-06-15T00:00:00Z.
Side effect: Any discover case included in the response is
automatically claimed — it transitions to pending_investigation
and an investigation record is created. Repeated polling of the
same case is safe; already-claimed cases are not double-counted.
Authorizations
Domain-scoped API key. Generate and manage keys from the API Keys page in Settings.
Accepted in two forms:
X-API-Key: <key>header (preferred)Authorization: Bearer <key>header (also accepted)
Query Parameters
Filter by user email or UPN.
Filter by TOTAL user identifier. If combined with email, both must refer to the same user.
Lifecycle state of a case:
discover— Vetted by the AI judge, ready for triagepending_investigation— Swiped; investigation pendinginvestigating— Investigation underwayenforced— An enforcement action has been takenclosed— Case closed
Case classification from the AI judge (Predict / inference pipeline).
Known values: threat, insider_threat, identity_vulnerability.
Older or demo rows may still carry legacy strings until backfilled.
Return cases whose created_at is greater than or equal to this timestamp.
Return cases whose created_at is less than or equal to this timestamp.
x <= 200Case id from the last item of the previous page.

