List the operations that failed or never got an answer

The operations queue: one row per token operation that stopped moving, newest first, so money that stopped is found rather than sitting unnoticed.

Outstanding cases

This is not the transaction log filtered. The log describes operations; this describes the things that went wrong with them, and only it can say when an operation went wrong. It lists work that is still outstanding — once the underlying case is resolved the row leaves the queue.

Reason codes

Every outstanding case is reported, whatever its reason. reasonCode is an open set: mostly the platform's own failure codes, plus RECON for an operation the ledger cannot account for (not raised since 2026-10-12 — see reasonCode). Treat an unfamiliar value as news rather than an error, and use reason to narrow the queue yourself.

Case details

Each row carries the case's own detail: a free-form JSON object holding whatever the path that opened it recorded — the node's own words, the producer's code, the attempt count, the nonce. Its keys differ by case, so there is no schema to bind to; read it defensively.

Query Params
string
length ≤ 64

Filter to one reason code, matched exactly and folded to upper case. The set is open, so an unrecognised code returns an empty page rather than a 400 — check the spelling against a row you have seen.

string
length ≤ 128

Filter to operations originating from this account. An operation naming it as the counterparty of a transfer is not matched.

date-time

Inclusive lower bound on occurredAt, as an ISO-8601 instant. An occurredAt from a response can be sent back here as it is.

date-time

Exclusive upper bound on occurredAt, as an ISO-8601 instant. The window is half-open, so consecutive ranges tile a timeline without a row falling into both or neither.

integer
≥ 0
Defaults to 0

Zero-based page index.

integer
1 to 100
Defaults to 20

Page size. A value above the maximum is rejected, not clamped.

Headers
string
required
^\d+\.\d+\.\d+$

The version of the Quant Flow API the request follows, as major.minor.patch (for example 1.0.0). The request is interpreted, and the response shaped, according to that version.

Responses

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