limit and page query parameters. Every paginated response includes metadata at the top level so you always know how far through the full dataset you are.
Query Parameters
Appendlimit and page to any list endpoint URL to navigate result sets. Both parameters are optional; the API falls back to sensible defaults if you omit them.
Response Metadata
Every paginated response wraps the results array alongside three top-level metadata fields. Use these fields to determine whether more pages exist and to build progress indicators.
A typical paginated response looks like this:
Pool List Response
Paginating Through Pools
The example below fetches every pool on Ethereum by walking forward through pages until the accumulated count meets thetotal returned by the API.
Paginating Through Transactions
Transactions endpoints support a higher maximumlimit of 200 per page, which is useful when iterating through high-volume pools.
For large transaction datasets, using
from_timestamp and to_timestamp query parameters is significantly more efficient than page-based iteration. Time-range queries allow the API to use indexed scans rather than offset-based lookups, reducing both latency and quota consumption on your end.