get
https://public-api.birdeye.so/defi/v3/token/meta-data/single
Retrieve metadata of a specified token.
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
Lightweight token identity lookup.
- Always use the checksum contract address on EVM chains and the canonical token mint address on Solana-like chains.
- Token metadata can vary by chain and token standard.
- Response may be
nullor missing fields if metadata is not indexed or unavailable. - Use this endpoint when fetching metadata for one token; use the multiple endpoint for batch lookups.
- Cache token metadata where possible because it changes less frequently than market data.
- Lite
- Starter
- Premium
- Business
- Enterprise
All chains ⛓️ ✨
Compute Unit ⚙️
- 3 CU per request.
Use Cases 💡
- Display token names, symbols, decimals, and logos in portfolios, token pages, and trading interfaces.
- Enrich search results, watchlists, and token cards before adding price or liquidity data.
- Normalize token display across chains using one metadata lookup pattern.
- Validate token identity before running analytics, alerts, or token-screening workflows.
How to Use 🛠️
- Provide
addressas the token address and setx-chainfor the target network. - Use the multiple metadata endpoint when you need to hydrate a list of tokens.
- Cache metadata because it changes much less often than price, liquidity, or trading activity.
Best Practices ✅
- Fetch metadata before rendering token tables so users see readable names and symbols instead of raw addresses.
- Join metadata with market-data or price endpoints for richer token cards.
- Store decimals with the token record so downstream amount formatting stays consistent.