Skip to main content
POST
Blockchain - Multiple Account Details
  • 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.
  • 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.
  • Send the address list in the addresses array.
  • Keep the list deduplicated so each account appears once in the response map.
  • Read each returned object’s owner, data_parsed, and decode_error to classify the account quickly.
  • Join the result back to your own watchlist by address, not by array position.
  • 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.
  • Solana only.

Authorizations

X-API-KEY
string
header
required

API key for authentication

Body

application/json
addresses
string[]
required

Solana account addresses. Maximum 100 addresses.

Required array length: 1 - 100 elements

Response

Successful response

success
boolean
required
data
object
required