Migrating from OneBalance to Zerion API

OneBalance backend services are being deprecated on May 18, 2026. If your app depends on it for balance reads, asset lists, or transaction history, you have a deadline to migrate. Zerion API covers the data layer of what OneBalance offered: positions and history across 40+ chains, including Solana, under one normalized schema.

This guide walks through what Zerion API can replace and how to map your existing calls.

What Zerion API covers

Zerion API provides wallet data across EVM chains and Solana under a single schema. 

The endpoints most relevant to a OneBalance migration are:

• Portfolio aggregation: /v1/wallets/{address}/portfolio returns total portfolio value across all chains, USD-valued, in a single call.
• Positions: /v1/wallets/{address}/positions/ returns token holdings and DeFi positions across chains.
• Transaction history: /v1/wallets/{address}/transactions/ returns clean, human-readable history.
• Asset list: /v1/fungibles/ returns the full fungible token universe.

Zerion API covers 40+ chains, including Solana. By default, all endpoints return unified response across all chains. For example, if you call the positions for a 0x… address, the response will return positions across all supported EVM chains. No manual stitching is needed. 

Zerion API endpoint mapping to OneBalance 

The most common OneBalance endpoints map cleanly to Zerion equivalents:

https://be.onebalance.io/api/assets/list → https://api.zerion.io/v1/fungibles/

https://be.onebalance.io/api/v3/balances/aggregated-balance → https://api.zerion.io/v1/wallets/{address}/portfolio

https://be.onebalance.io/api/v3/status/get-tx-history → https://api.zerion.io/v1/{address}/transactions/

The portfolio endpoint returns total value across all chains in one call, USD-valued. For wallet headers, net worth displays, and dashboard summaries, this is a direct replacement for the OneBalance aggregated-balance flow.

One difference worth flagging: if you need "total USDC across all chains" specifically (rather than the portfolio value in USD), call the Zerion API positions endpoint and group results client-side by fungible_id. The grouping is a few lines of code and gives you finer control than the OneBalance abstraction did.

Fiat prices 

Most Zerion API endpoints return USD values out of the box. So no separate provider is needed for fiat prices.  

What Zerion API doesn't cover

However, Zerion API specializes in wallet data and doesn’t replace OneBalance’s chain abstracted execution capabilities.

Specifically, you also need to get another provider for: 

• Multi-chain swaps 
• Multi-chain contract calls

OneBalance recommends using Relay for execution alongside Zerion API for data.

Alternatively, if you already use Privy or Turnkey for embedded wallets, you can (partially) migrate to their swap and call flows and supplement them with Zerion API for aggregated multichain data. 

Step-by-step migration process

Here is what you need to migrate from OneBalance: 

1. Get a Zerion API key and transform it for Basic Authentication
2. Swap balance reads for https://api.zerion.io/v1/wallets/{address}/portfolio.
3. Swap asset list calls for https://api.zerion.io/v1/fungibles/.
4. Swap transaction history for https://api.zerion.io/v1/{address}/transactions/.
5. Integrate another transaction execution provider (e.g. Relay) into the execution flows that were previously routed through OneBalance.

If you use Pimlico, you can leave the existing bundler and paymaster as-is. Neither the Zerion API migration nor the OneBalance shutdown affects that layer.

Try it now

Get a free Zerion API key and see it in action. 

The Zerion API documentation also includes detailed endpoint reference, code samples, and recipes. 

If you’re working through a large migration and want to talk through edge cases, start a new chat in the Zerion API dashboard, and we’ll be happy to help.