post
https://public-api.birdeye.so/blockchain/v1/account/detail/multiple
Returns account details for up to 100 Solana addresses.
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
- Batch version of account detail for up to 100 Solana addresses per request.
- Response is a map keyed by address, so missing or unparseable accounts are easy to detect without preserving request order.
- Parsed account data is returned only when Birdeye has a decoder for that account layout.
- Use this endpoint when auditing multiple PDAs, pools, vaults, or launchpad accounts at once.
- Starter
- Premium
- Business
- Enterprise
Solana
Use Cases 💡
- Hydrate a protocol dashboard with many program accounts in one request.
- Batch-inspect pools, vaults, fee accounts, and PDAs during monitoring or indexing.
- Validate account ownership and decoded state across a watchlist of protocol accounts.
- Speed up support, research, and forensic workflows that need multiple account snapshots together.
How to Use 🛠️
- Send the address list in the
addressesarray. - Keep the list deduplicated so each account appears once in the response map.
- Read each returned object's
owner,data_parsed, anddecode_errorto classify the account quickly. - Join the result back to your own watchlist by address, not by array position.
Best Practices ✅
- Chunk large crawls into batches of up to 100 addresses.
- Reuse the single-account endpoint only for ad hoc inspection; use this one for systems and dashboards.
- Group addresses by expected program owner so downstream parsing and validation stay simpler.
Limitations ⚠️
- Solana only.