List token operations

Returns a page of the organisation's operations, newest first with transactionId as a tiebreaker. Ordering is fixed; there is no sort parameter. Note this is the opposite of the account and customer listings, which are oldest first.

Pagination

Two paging styles, chosen by which parameters are present. Offset (page/size) returns the totals envelope, unchanged. Cursor (cursor/limit) pages the way the webhook endpoints do: the response carries items and a nextCursor to send back for the following page, has no totals, and never repeats or skips a row when operations arrive mid-walk.

Page until nextCursor is null. Naming parameters from both styles is a 400; naming neither is the offset listing's first page.

Cursor consistency

A cursor is opaque and bound to the filters it was minted under — sent back with different filters it is a 400, never silently wrong pages.

Filtering

The three filters are optional, combine, and work with either style. An unrecognised state or txType is a 400. A filter matching nothing returns an empty page, not a 404.

Response shape

Each row is the same shape a single read returns.

Query Params
string
enum

Filter by the operation's state.

string
length ≤ 128

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

string
enum

Filter by operation type.

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.

string

The nextCursor from the previous page. Omit it for the first page. The cursor is opaque: never construct or parse one. A token this endpoint did not issue, or one replayed after the filters changed, returns 400.

integer
1 to 100
Defaults to 20

Page size. Defaults to 20, maximum 100. A value outside that range is rejected with 400, 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