get
https://public-api.birdeye.so/defi/v3/token/meta-data/multiple
Retrieve metadata of multiple tokens. Maximum 50 addresses.
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
Batch token identity lookup.
- 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 50 token addresses per request.
- Token metadata can vary by chain and token standard.
- Response entries may be
nullor missing fields if metadata is not indexed or unavailable for a token. - Use this endpoint for batch metadata lookups across token lists, watchlists, search results, or portfolio rows.
- Cache token metadata where possible because it changes less frequently than market data.
- Premium
- Business
- Enterprise
All chains ⛓️ ✨
Compute Unit ⚙️
- Batch CU is calculated as
ceil(3 * token_count^0.8).
Use Cases 💡
- Hydrate token lists with names, symbols, decimals, and logos in one request.
- Prepare metadata for portfolio, screener, and watchlist pages.
- Reduce request volume when loading many token cards at once.
- Join metadata with price, volume, and liquidity data for richer token tables.
How to Use 🛠️
- Set
x-chainfor the target network. - Pass
list_addressas comma-separated token addresses. - Cache returned metadata and refresh it less frequently than market metrics.
Best Practices ✅
- Use this endpoint before batch market-data calls so every row has readable token identity.
- Deduplicate token addresses before calling to keep requests clean.
- Store token decimals from metadata as shared formatting context for balances, prices, and quantities.