Royalty distributions and claims, paginated independently
Both streams newest first. The filters apply to both; the cursors do not — each stream has its own. See the `RoyaltyFlow` schema for why this does not use the shared pagination shape.
v1/datasets/{id}/royalty-flowPath Parameters
idRequiredstring
The dataset version's 32-byte id.
"^0[xX][0-9a-fA-F]{64}$"Query Parameters
tokenstring
Filter to one payment token. native or a 0x ERC-20 address.
frominteger
Inclusive lower bound on block number. Omitting it is distinct from
passing 0, so block 0 remains a usable filter value. Must be <= to.
0Format: "int64"tointeger
Inclusive upper bound on block number.
0Format: "int64"limitinteger
Page size. Server-configured default and ceiling (API_DEFAULT_LIMIT /
API_MAX_LIMIT; 50 and 200 unless overridden). A value above the ceiling
is silently clamped, not rejected — check pagination.limit in the
response rather than assuming the requested value was honoured. Values
below 1, or non-integers, are a 400.
1distCursorstring
Cursor for the distributions stream only. Note the name — this endpoint
does not accept cursor.
claimCursorstring
Cursor for the claims stream only.
One page of each stream.
Last updated