Ply · sample

getTokenAccountsByOwner

Source: solana.com/docs/rpc/http/gettokenaccountsbyowner · read 3 Sep 2026

What it is

JSON-RPC method that returns SPL token accounts owned by a pubkey. Filter is required: either a mint, or a token program id (classic Tokenkeg… or Token-2022). Optional config: commitment, encoding, minContextSlot, dataSlice.

What it claims

• jsonParsed returns {program, parsed, space}. Program is spl-token or spl-token-2022. If no parser exists, the node falls back to base64.
• Each row has the token-account pubkey plus account wrapper: lamports, owner program, space. Parsed info includes mint, owner, state (uninitialized / initialized / frozen), tokenAmount, optional delegate, closeAuthority, extensions.
• Classic account data is 165 bytes. The example account holds 2,039,280 lamports — the usual rent-exempt reserve.
• Examples on the page call devnet, not mainnet.

What is missing

• No pagination. A wallet with many ATAs is one response; public RPC may truncate or 429.
• Token-2022 is mentioned as a parser name, but the filter examples only show the classic Token program. You still need a second call with TokenzQd… for 2022 accounts.
• No note that amount "0" accounts still hold those lamports until closed.

A paid Ply brief is this shape: what it is, what it claims, what is missing. One page. Sources in the open.

Back to Ply