getMultipleAccounts

POSTAccountsOperator+

Returns account info for up to 100 addresses in a single call.

Try itSends a real request from your browser to the selected region.
POST
/

getMultipleAccounts batches up to 100 getAccountInfo lookups into one round trip, returning results in the same order as the input addresses.

Every result comes from the same bank slot, giving a consistent snapshot across related accounts.

Plans & rate limitsOperator and above
FreeNot included
Operator50/s
Blade Runner200/s
Nexus500/s

Parameters

params is a JSON array, with values in this order: addresses, config.

1addressesstring[]required

Up to 100 addresses to look up, base-58 encoded.

Maximum: 100
2configobject

Optional configuration.

Show propertiesProperties
commitmentstringdefault: "finalized"

Bank state to read the accounts from.

Allowed values:finalizedconfirmedprocessed
encodingstringdefault: "base58"

How to encode each account's data. Same rules as getAccountInfo: base58 fails for accounts over 129 bytes.

Allowed values:base58base64base64+zstdjsonParsed
dataSliceobject

Return only a byte range of each account's data. Not valid with jsonParsed.

Show propertiesProperties
offsetintegerrequired
lengthintegerrequired
minContextSlotinteger

Minimum slot the node must have processed before answering.

Result

resultobject

Accounts wrapped with context, in the same order as the input addresses.

Show propertiesProperties
contextobjectrequired
Show propertiesProperties
slotinteger
apiVersionstring
value(object | null)[]required

One entry per input address, in order. An entry is null if that account doesn't exist.

Show one ofOne of
Option 1object
Show propertiesProperties
lamportsinteger
ownerstring
executableboolean
rentEpochinteger
spaceinteger
dataany

Same shape as in getAccountInfo: a [base64String, encoding] tuple, or a parsed object for jsonParsed.

Option 2null

Notes

  • Maximum 100 addresses per call — split larger batches client-side.
  • Not available on the Free plan.
  • The Wrapped SOL mint's supply field reads 0 regardless of how much is wrapped, since wrapped SOL is tracked via each token account's lamport balance, not the mint's supply counter.