getTokenAccountsByOwner

On Solana — the high-throughput chain secured by Proof-of-History and Proof-of-Stake, with SOL as its native token — getTokenAccountsByOwner returns the token accounts owned by an address, filtered by mint or program. Because every SPL token a wallet holds lives in its own data account rather than a single balance map, this is the standard way to enumerate a wallet's holdings. Send a JSON-RPC 2.0 request with positional params to https://solana.therpc.io/YOUR_API_KEY, passing the owner pubkey plus a filter of either { mint } or { programId }, and you get an array of { pubkey, account } entries.

Use cases

• List all of a wallet's SPL token holdings by filtering on the SPL Token programId (TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA).
• Find the specific token account a wallet uses for one mint — for example, locating a user's USDC account before building a transfer.
• Build a token-portfolio view with readable balances by requesting encoding: "jsonParsed", which decodes amount, decimals, and mint inline.

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": "getTokenAccountsByOwner",
8  "params": [
9    "9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM",
10    {
11      "mint": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v"
12    },
13    {
14      "encoding": "jsonParsed"
15    }
16  ]
17}'

Errors & troubleshooting

Common pitfalls

• The filter must contain exactly one of mint or programId — passing both, or an empty object, yields an Invalid params (-32602) error.
• Token-2022 accounts live under a different program (TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb) than classic SPL Token. To cover a wallet completely, query both program IDs and merge the results.

Supported networks

• Mainnet
• Devnet

See also

• getTokenAccountsByDelegate
• getTokenAccountBalance
• getProgramAccounts