Paginated lists
Endpoints that return a long list of already computed results are paginated withoffset and limit. For example,
POST /v1/counterparties, which returns all counterparties of an address, sorted by USD value:
offset = next_offset until has_more is false. limit accepts up to 100.
Each page is a query and is charged. If the source cannot read the address, the response is
503 source_unavailable, never «0 counterparties».Capped reads
To build a trace, the API reads each address’s history from the data sources. That read has a row cap per list. When an address has more activity than fits, part of its history is not read, and the response declares it indegraded_sources and on the affected node (coverage_gaps):
Each cutoff’s message says which blocks of which list are missing. Whatever was left out is not «no movements».
The read focuses on the trace: on a cut-off node, it first reads from the block where the traced funds arrived
forward (or from where they left, backward). That way the cap is spent on what matters for following the money, not
on the address’s newest activity.
«Read more»
To keep reading a node that ended withtransfers.truncated, request it again in POST /v1/trace as address, with
its since and with read_more:
Extra read steps for the seed node: each step adds another row cap per list. It goes from 0 to 9; a larger value is
capped.
With
false it does not expand forward and only reads backward (back_hops): useful to re-read a parent.read_more (2, 3…).
In the web app it is the node’s Leer más (read more) button.
Other declared caps
Some responses cap their inner lists so they do not grow without limit. When they cut, they say so with a field of their own:- a total counter and the trimmed list (for example,
discarded_totalwithcandidates_truncated: true); *_truncated: truewhen a list was cut (refs_truncated,contracts_truncated);- a summary of what was dropped, such as
unpricedin counterparties: how many rows of tokens without a published price were left out, and from which contracts.