List and search Cases

Returns one page of your organization's Cases with the total row count for the filter set. Filter by status or work-queue stage, investigator, network and address, client reference, priority, mute state, and creation or last-modified time windows; pagination is 1-based page/pageSize. To poll for changes, filter on updatedFrom/updatedTo and overlap successive windows rather than resuming exactly where the last poll stopped — a Case can appear in more than one poll.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string
string
string

Network filters independently. Address further narrows that filter and
requires network; address without network is INVALID_ARGUMENT. Both are
exact after canonical resolution/normalization. Network keys and aliases
resolve to the Subject's chain class, so ethereum_mainnet, for example,
matches EVM Cases across member networks. The match tolerates both Subject
vocabularies: a Case stored under the concrete network key or
under its chain class key is found either way.
An address that cannot be valid on the requested network produces a
successful empty page — no such Subject can exist — while an unknown
network name stays INVALID_ARGUMENT.

string
string
enum
Defaults to CASE_STATUS_UNSPECIFIED
Allowed:
date-time
date-time
int32
string
enum
Defaults to QUEUE_STAGE_UNSPECIFIED

Derived work queue filter. Mutually exclusive with status;
QUEUE_STAGE_UNASSIGNED is incompatible with investigatorId.

  • QUEUE_STAGE_UNSPECIFIED: No queue filter.
  • QUEUE_STAGE_UNASSIGNED: Open Cases with no Investigator assigned.
  • QUEUE_STAGE_ASSIGNED: Open Cases with an Investigator assigned.
  • QUEUE_STAGE_WAITING_FOR_APPROVAL: Cases pending Manager approval.
  • QUEUE_STAGE_CLOSED: Closed, non-archived Cases.
  • QUEUE_STAGE_ARCHIVED: Archived Closed Cases: the separate Archive view, retained indefinitely
    with complete evidence and audit history.
Allowed:
int32

1-based page number; 0 defaults to 1. Values above 10000 are rejected.

string
enum
Defaults to MUTED_FILTER_UNSPECIFIED

Mute filter. Omitted or MUTED_FILTER_UNSPECIFIED includes muted
Cases, MUTED_FILTER_EXCLUDE drops them, and MUTED_FILTER_ONLY returns only
them.

  • MUTED_FILTER_UNSPECIFIED: Include muted Cases (unfiltered default; hides nothing).
  • MUTED_FILTER_EXCLUDE: Exclude muted Cases from the result (default board / My Cases views).
  • MUTED_FILTER_INCLUDE: Include muted Cases explicitly.
  • MUTED_FILTER_ONLY: Only muted Cases (the Muted view).
Allowed:
string
enum
Defaults to CASE_PRIORITY_UNSPECIFIED

Exact Priority filter; CASE_PRIORITY_UNSPECIFIED means no
priority filter.

Allowed:
boolean

Manager-only Trash view. Default (false) excludes deleted Cases
from every list; true selects only deleted Cases (Trash). deletedOnly
composes with the other filters but is rejected together with queueStage,
since Trash is not a work queue. A non-Manager requesting it is denied.

boolean

Hides Closed Cases, which is what "every Case still in play" needs.

Neither status nor queueStage can express it: both are single-valued, so
neither can name the several active stages at once, and there is no negation.
This covers archived Cases too — a Case is only ever archived after being
closed, so archived is a strict subset of Closed.

Rejected together with a Closed status or the CLOSED / ARCHIVED
queueStage: those pin the status to CLOSED, so the combination describes
the empty set, and a caller is better told than handed nothing.

date-time

Change-polling filter. Inclusive lower bound on the Case's
last-modified instant, which moves on every status transition, metadata
edit, and workflow action. Sending it with status=CASE_STATUS_CLOSED
finds Cases that are Closed and were last modified since a previous run,
regardless of when they were created; scanning it without a status filter
also surfaces reopened Cases, at the cost of a slower query (the index is
optimized for status-bound ones).

The instant is stamped when a write starts, not when it commits, so a write
that commits after a read is not in that read. Overlap the window rather
than resuming exactly where the last run stopped, and expect to see some
Cases more than once.

Validation mirrors the created range: from must not be after to.

date-time
Response

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json