Pagination, filtering, sorting, and currency

Most Zerion API list endpoints return paginated results and support filtering. This page covers the patterns you’ll use across the API.

Pagination

List endpoints use cursor-based pagination. Each response includes a links object with URLs for navigating between pages.

How it works

Make your initial request without any page parameter
Check links.next in the response - if present, there are more results
Follow the links.next URL directly to get the next page
Repeat until links.next is absent

Response with pagination

{
  "links": {
    "self": "https://api.zerion.io/v1/wallets/0x.../positions/?page[size]=10",
    "next": "https://api.zerion.io/v1/wallets/0x.../positions/?page[size]=10&page[after]=eyJhZnR..."
  },
  "data": [...]
}

Control the number of results per page with page[size]:

Parameter	Type	Default	Min	Max
`page[size]`	integer	`100`	`1`	`100`

Do not construct page[after] cursor values manually. Always use the full URL from links.next - cursor tokens are opaque and may change format without notice.

Iterating through all pages

async function fetchAll(url, apiKey) {
  const results = [];

  while (url) {
    const response = await fetch(url, {
      headers: { Authorization: `Basic ${btoa(`${apiKey}:`)}` }
    });
    const json = await response.json();
    results.push(...json.data);
    url = json.links.next || null;
  }

  return results;
}

const positions = await fetchAll(
  "https://api.zerion.io/v1/wallets/0x.../positions/?page[size]=100",
  "YOUR_API_KEY"
);

import requests

def fetch_all(url, api_key):
    results = []

    while url:
        response = requests.get(url, auth=(api_key, ""))
        data = response.json()
        results.extend(data["data"])
        url = data["links"].get("next")

    return results

positions = fetch_all(
    "https://api.zerion.io/v1/wallets/0x.../positions/?page[size]=100",
    "YOUR_API_KEY"
)

Filtering

Filter parameters use the filter[field] syntax. Pass multiple values as comma-separated:

?filter[chain_ids]=ethereum,base&filter[position_types]=deposit,staked

Common filters include chain_ids, position_types, operation_types, trash, search_query, and fungible_ids. Each endpoint documents its available filters and accepted values in the relevant API reference page, such as wallet positions, wallet transactions, or fungibles search. For spam filtering behavior, see the spam filtering guide.

Keep the request URL short. Filters are applied server-side and travel in the query string, so a wide filter set (many chain IDs, many fungible IDs) can produce a very long URL. Stay under 2000 characters, which is safe across virtually every combination of client and server. Past that, requests can be truncated or rejected before they reach the API. Split a large filter list across several requests instead.

Sorting

Some endpoints support a sort parameter. Prefix with - for descending order:

?sort=-market_data.market_cap

Available sort fields vary by endpoint - check the relevant list endpoint in the API reference, such as wallet positions or wallet transactions, for supported options.

On wallet positions, use sort=value (the default) to get the most valuable positions first. Positions without a reliable price have value: null and sort last.

Currency

Most endpoints that return monetary values accept a currency parameter. Default is usd.

?currency=eur

Supports major fiat currencies and eth/btc. See any currency-aware endpoint, such as wallet positions, for the full list.

Get Started

Core Concepts

Migrating to Zerion API

Pagination, filtering, sorting, and currency

How it works

Iterating through all pages

Filtering

Sorting

Currency

​Pagination

​How it works

​Iterating through all pages

​Filtering

​Sorting

​Currency

Pagination

How it works

Iterating through all pages

Filtering

Sorting

Currency