getMultipleAccounts

getMultipleAccounts is the batched form of getAccountInfo on Solana: it reads many accounts in a single call instead of one request per address. You pass an array of base-58 public keys and get back an array of account objects — each with data, owner, lamports (native SOL, where 1 SOL = 1,000,000,000 lamports), executable, rentEpoch, and space, or null for any address that does not exist — returned in the same order as the input. It is the efficient way to hydrate a set of known accounts over Solana's high-throughput, ~400ms-slot network. Call it as a JSON-RPC 2.0 POST with positional params against https://solana.therpc.io/YOUR_API_KEY, choosing base64 for raw bytes or jsonParsed for decoded data.

Use cases

• Read many SPL Token accounts or PDAs in one round-trip instead of firing a separate getAccountInfo per address.
• Hydrate a wallet portfolio view — all of a user's token balances at once — with a single batched request rather than N calls.
• Fetch a fixed set of program accounts whose addresses you already know (for example a list of market or pool accounts) in one request.

Parameters

Response

Example request

1curl https://solana.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5  "jsonrpc": "2.0",
6  "id": 1,
7  "method": "getMultipleAccounts",
8  "params": [
9    [
10      "9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM"
11    ],
12    {
13      "encoding": "base64"
14    }
15  ]
16}'

Errors & troubleshooting

Common pitfalls

• There is a per-call cap on how many addresses you can pass (typically around 100) — split larger sets into chunks and merge the results client-side.
• Results are positional and can contain null entries for accounts that do not exist; match each returned item back to its input address by index, never by assuming a one-to-one non-null mapping.

Supported networks

• Mainnet
• Devnet

See also

• getAccountInfo
• getProgramAccounts