getTransfersByAddress
getTransfersByAddress
Query parsed, human-readable token and native SOL transfer objects by address with filters by mint, time, amount, counterparty, and pagination.
POST
getTransfersByAddress
Overview
getTransfersByAddress returns parsed, human-readable transfer objects for token and native SOL movement involving a wallet address. Use filters to narrow results by mint, block time, amount, slot, direction, or counterparty. The response is designed for accurate wallet activity views, payment tracking, and balance reconciliation without reimplementing Solana transfer parsing.
Mint and burn transfers are one-sided. Mints have
fromUserAccount: null and can only be returned as inbound transfers for the recipient. Burns have toUserAccount: null and can only be returned as outbound transfers for the burning owner.Request Parameters
Base58-encoded owner wallet address to query transfers for. Pass the wallet owner address, not an associated token account (ATA).
Filter by counterparty address. Returns only transfers to or from this address.
Filter by transfer direction relative to the queried address.
inoutany
Token mint address. Use So11111111111111111111111111111111111111111 for native SOL and So11111111111111111111111111111111111111112 for WSOL.
SOL/WSOL display mode. merged treats WSOL as native SOL and excludes wrap/unwrap rows so SOL-denominated history is easier to reconcile; separate preserves WSOL as a distinct SPL token mint and includes wrap/unwrap rows.
mergedseparate
Additional filters for amount, block time, and slot.
Range comparison filter. All fields are optional and can be combined.
Greater than.
Greater than or equal.
Less than.
Less than or equal.
Range comparison filter. All fields are optional and can be combined.
Greater than.
Greater than or equal.
Less than.
Less than or equal.
Range comparison filter. All fields are optional and can be combined.
Greater than.
Greater than or equal.
Less than.
Less than or equal.
Maximum number of transfers to return. Range 1 to 100.
Cursor from the previous response for pagination.
Data commitment level.
finalizedconfirmed
Minimum context slot to use for request (optional).
Result ordering.
ascdesc
Authorizations
Body
application/json
The JSON-RPC protocol version.
Available options:
2.0 Example:
"2.0"
A unique identifier for the request.
Example:
"1"
The name of the RPC method to invoke.
Available options:
getTransfersByAddress Example:
"getTransfersByAddress"
Array containing the required wallet address and optional configuration object.
Example:
[
"86xCnPeV69n6t3DnyGvkKobf9FdN2H9oiVDdaMpo2MMY",
{
"mint": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
"limit": 50,
"sortOrder": "desc"
}
]Previous
OverviewComplete reference for all Solana JSON-RPC HTTP methods available through Helius. Account data, blocks, transactions, tokens, epochs, and system information.
Next
getTransfersByAddress