Skip to main content
Collection endpoints use offset pagination. Error responses use the HTTP status code and a JSON object containing an error string.

​
Pagination

Pass limit and offset as query parameters:
Pool listing accepts 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.

​
Error shape

Errors use this general structure:

​
Retry policy

Retry network failures, 429, and transient 5xx responses with exponential backoff and jitter. 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.