When to use batch endpoints
Choose the request shape that matches your input list:Portfolio Tracker
Fetch a wallet’s positions across 50+ tokens in one call
Token Dashboard
Get how 200 wallets performed on a specific token
Leaderboard Enrichment
Look up specific wallet+token pairs from leaderboard results
- Position batches return token-level position rows and support
pnlMode. - Wallet summary batch returns wallet-level summaries and wallet tags for up to 100 wallets. It does not accept
pnlMode.
One wallet, many tokens
Use wallet batch positions for one wallet and a list of mints.notFound array. Missing items are listed there; they are not request errors.
Many wallet summaries
UsePOST /v2/pnl/wallets/batch when you only need wallet-level summaries and tags, not per-token positions. The request accepts up to 100 unique wallet addresses. Invalid addresses are returned in invalid, wallets without a PnL summary are returned in notFound, and requests with more than 100 unique valid wallets include a truncated object.
wallet, identity, summary, tags, and updatedAt.
The batch response includes
summary only. The analysis block from the single-wallet endpoint — including analysis.winRate, analysis.tokens.profitable, analysis.tokens.losing, analysis.maxSinglePnl, and the ending / pnlAdjustments fields — is not returned by POST /v2/pnl/wallets/batch. If you need winRate or any other analysis.* field for multiple wallets, call GET /v2/pnl/wallets/{wallet} once per wallet.One token, many wallets
Use token batch positions to compare how multiple wallets performed on the same token.Any wallet-token pairs
Use position batch lookup for a list of wallet-token pairs.Which endpoint to use
PnL mode
All three position batch endpoints accept?pnlMode=strict|adjusted|raw as a query parameter. Default is strict. The wallet-summary batch endpoint does not accept pnlMode. See the Essentials for what each mode does.
Trader rankings
Build a shortlist of wallets to batch-enrich.
Wallet PnL
Drill into a single wallet from your batch results.