Skip to main content
The Zerion API provides real-time, normalized access to onchain data through RESTful endpoints. All requests go to https://api.zerion.io and require authentication via HTTP Basic Auth. Responses follow the JSON:API specification.

​
Endpoint categories

​
Wallets

Portfolio, positions, transactions, PnL, and NFTs — all scoped to a wallet address. This is the core of the API. Positions include both fungible tokens and DeFi protocol positions. NFT data is split into individual holdings, collections, and a portfolio summary. All positions and transactions come with icons, labels, links, metadata, and relationships. Everything is ready to be immediately used in interfaces without additional interpretation or enrichment.

​
Fungibles

Token metadata, pricing, and market data. Search and filter across all supported tokens, look up by Zerion ID or by chain and contract address, and fetch historical price charts.

​
Chains

The full list of supported blockchains with metadata. Useful for populating chain selectors or validating chain IDs before making other calls.

​
NFTs

Look up individual NFTs by reference or unique ID, with support for batch fetching.

​
Swap & Bridge

Quotes for token swaps and cross-chain bridges, routed across DEXs and bridge protocols. First check which tokens are available for a route, then request offers.

​
Gas Prices

Current gas price estimates across all supported chains. Useful for displaying fee estimates or optimizing transaction timing.

​
DApps

Metadata for decentralized applications — names, icons, and categories. DApp info is also embedded in position and transaction responses to provide context.

​
Subscriptions (Webhooks)

Push-based notifications for wallet activity — no polling required. Create subscriptions, manage which wallets and chains to monitor, and update webhook URLs.

​
Response structure

Every response follows a consistent JSON:API format: 
{
  "links": {
    "self": "https://api.zerion.io/v1/...",
    "next": "https://api.zerion.io/v1/...?page[after]=..."
  },
  "data": {
    "type": "positions",
    "id": "unique-id",
    "attributes": { ... },
    "relationships": { ... }
  }
}
FieldDescription
linksPagination — self for the current page, next for the next page
dataA single resource object or an array of them
typeResource type (e.g., positions, transactions, fungibles)
idUnique identifier for the resource
attributesThe resource’s data fields
relationshipsLinks to related resources

​
Next steps

Pagination & Filtering

Paginate results and apply filters.

Error Handling

Error codes and how to handle them.

Rate Limits

Request limits and how to stay within them.