post
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 request-body input.
- This is the POST variant of
Price - Multipleand is useful when the token list is easier to send in a JSON payload. - Always use checksum contract addresses on EVM chains and canonical token mint addresses on Solana-like chains.
- Maximum batch size is
100token addresses per request. include_liquidity=truerequests price plus liquidity context for each token when available.- Individual response entries may be
nullor partial if a token is unknown, unsupported, or not yet indexed.
- 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 many tokens from backend jobs, refresh workers, or API gateways that already hold JSON arrays.
- Hydrate portfolio pages, watchlists, and token grids with one network round trip.
- Support screening systems that need current price snapshots before ranking or filtering assets.
- Lower request overhead when multiple app surfaces need the same batch at once.
How to Use 🛠️
- Set
x-chainfor the target network. - Send the token list in the POST body using the documented request schema.
- Keep the request under
100addresses. - Use the GET variant when a simple comma-separated query string is more convenient.
Best Practices ✅
- Normalize addresses before batching so you do not waste slots on duplicates or invalid casing.
- Reuse the same batch response across multiple UI components during the same refresh cycle.
- Prefer this POST form when URL length becomes awkward with large token sets.