Skip to main content
Most collection endpoints use offset pagination. The Explore transaction feed uses a cursor. Error responses contain an error string and can include a machine-readable code.

Offset pagination

Pass limit and offset as query parameters:
Pool listing and Explore token and pool lists accept a page size from 1 through 100. Begin with offset 0, advance the offset by the number of returned items, and stop when the response metadata or an empty page indicates completion. Do not assume that an offset identifies a permanent snapshot. New indexed activity can change collection ordering while a bot paginates. For reconciliation jobs, record stable resource identifiers and tolerate duplicates between pages.

Explore transaction cursor

Request GET /explore/transactions?limit=50 for the first page. Pass the returned nextCursor as the cursor query parameter for the next page. Stop when nextCursor is null. Do not calculate a cursor or use an offset for this feed. Keep the window, type, token, and pool filters unchanged between pages. Supported windows are 1h, 1d, 1w, and 1m. Start a new request without a cursor when you change a filter.

Error shape

Errors use this general structure:

Retry policy

Retry network failures, 429, and transient 5xx responses with exponential backoff and jitter. Honor Retry-After when present. An oracle twap_not_deployed error requires deployment support before the request can succeed. Set both a request timeout and a maximum number of attempts. Do not automatically retry non-idempotent write requests unless the endpoint provides an idempotency mechanism or the client can prove the previous attempt did not take effect.

Large integers

Preserve token amounts, liquidity values, and other on-chain integers exactly. When a response represents an integer as a JSON string, parse it with an arbitrary-precision integer type such as JavaScript BigInt rather than number.