get
https://public-api.birdeye.so/defi/multi_price
Retrieve the latest price information for multiple tokens. Maximum 100 tokens
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
Batch spot pricing with query-string input.
- Always use checksum contract addresses on EVM chains and canonical token mint addresses on Solana-like chains.
- Pass token addresses as a comma-separated list in
list_address. - Maximum batch size is
100token addresses per request. include_liquidity=truerequests price plus liquidity context for each token when available.- Individual entries may be
nullor partial if a token is unknown, unsupported, or not indexed on the selected chain.
- Lite
- Starter
- Premium
- Business
- Enterprise
All chains ⛓️ ✨
Compute Unit ⚙️
- Batch CU is calculated from a base of
3 CUper token-set request and scales with batch size.
Use Cases 💡
- Price entire watchlists, portfolio holdings, or leaderboard rows in one request.
- Feed token tables, mobile market boards, and scanner results without per-row price calls.
- Pair batch prices with batch market, liquidity, or metadata endpoints for dense dashboards.
- Reduce request fan-out for bots or backends that track many assets at once.
How to Use 🛠️
- Set
x-chainfor the target network. - Pass
list_addressas a comma-separated token-address string. - Keep the request under
100addresses. - Switch to the POST variant when your token list is easier to send in a request body.
Best Practices ✅
- Deduplicate token addresses before calling so CU and payload size stay predictable.
- Cache the batch result briefly and reuse it across cards, tables, and widgets rendered in the same cycle.
- If only a few rows need live updates, refresh those rows separately instead of reloading a full batch every time.