Batch token reads
Fetch one read (overview, security, holders, metrics, price, trade-data, markets or coverage) for up to 25 mints in a single call — for a portfolio dashboard, instead of N requests.
Pick ONE endpoint and pass the mints; we fan out to the same per-mint handler for each (so the shape is identical to the single-mint call) and return a map keyed by mint. Each mint counts as one request against your plan's rate limit, and a per-mint failure is captured in that mint's slot as { error, status } rather than failing the whole batch.
Query parameters
| Field | Type | Description |
|---|---|---|
networkoptional | mainnet | devnet | Network to read. Devnet returns an empty payload (with a note) until its ingestor lands. default mainnet |
Body
| Field | Type | Description |
|---|---|---|
mintsrequired | array | Base58 mint addresses (deduped; capped at 25 — extras are dropped with truncated:true). |
endpointoptional | overview | security | holders | metrics | price | trade-data | markets | coverage | Which per-mint read to fan out. default overview |
Response fields
| Field | Type | Description |
|---|---|---|
endpoint | string | The read that was fanned out. |
count | number | Number of mints resolved (after dedupe + cap). |
truncated | boolean | Present (true) when the list exceeded the 25-mint cap. |
data.{mint} | object | That mint's response for the chosen endpoint (same shape as the single-mint call), or { error, status } on a per-mint failure. |
One endpoint per call keeps the cost predictable (= number of mints). Call again with a different endpoint for another data type.
Requires an API key — batch reads on heavy endpoints aren't an anonymous surface.