Skip to main content
GET
cURL

Query Parameters

startTime
integer<int64>

Start time as Unix timestamp (milliseconds)

Required range: 0 <= x <= 4102444800000
endTime
integer<int64>

End time as Unix timestamp (milliseconds)

Required range: 0 <= x <= 4102444800000
pageSize
integer<uint32>
default:50

Items per page (max 1000)

Required range: 1 <= x <= 1000
orderBy
enum<string>
default:DESC

Sort direction for settledAt

Available options:
ASC,
DESC
Minimum string length: 1
pageToken
string

Pagination cursor with two states:

  • Omitted or empty string (""): start a cursor walk with no prior position, from the newest settlement (the oldest when orderBy is ASC).
  • Non-empty: an opaque cursor from a previous response's nextPageToken; results resume immediately after that position.

The walk seeks on (settled_at, id) in the requested direction. settled_at is NOT NULL and never changes once a window settles, and the id tie-break makes the key total — the removed page-number mode ordered by (settled_at, trading_pair_id, epoch) with no tie-break, so a page boundary between two settlements sharing that triple could repeat or drop a row.

total is populated — bounded by the server count ceiling, see totalCapped. Filters and orderBy must match the request that produced the token, or the request is rejected 400.

Response

200 - application/json

OK

records
object[] | null
total
integer<uint32> | null

Settlements matching the filter, bounded by the server count ceiling — see totalCapped. A lower bound when totalCapped is true.

pageSize
integer<uint32> | null
nextPageToken
string | null

Cursor for the next page, minted from the last row of an over-fetched page: this listing is one ordered read, so a page shorter than pageSize proves the walk is exhausted and this is empty.

totalCapped
boolean | null

True when MORE than the server ceiling matched, so the count stopped at the ceiling and total is a lower bound.