getTransactionsForAddress
getTransactionsForAddress
Enhanced transaction history API with powerful filtering, sorting, and pagination capabilities for retrieving comprehensive transaction data for any address. Supports bidirectional sorting, time/slot/status filtering, and efficient keyset pagination.
POST
getTransactionsForAddress
Request Parameters
Solana account address to retrieve transaction history for (wallet, token, program, NFT, etc.).
Level of transaction detail to return.
signaturesfull
Sort order for returned transactions.
ascdesc
The commitment level for the request. The
processed commitment is not supported.confirmedfinalized
Minimum context slot to use for request (optional).
Maximum number of transactions per request. Use 1–1000 for transactionDetails:“signatures” and 1–1000 for transactionDetails:“full”.
Pagination token from previous response to get next page of results (format “slot:position”).
Encoding format for transaction data (applies only when transactionDetails=full).
jsonjsonParsedbase58base64
Maximum transaction version to return (applies only when transactionDetails=full).
Advanced filters to narrow down transaction results.
Filter by slot number.
Greater than or equal to slot number.
Greater than slot number.
Less than or equal to slot number.
Less than slot number.
Filter by block timestamp (Unix timestamp).
Greater than or equal to timestamp.
Greater than timestamp.
Less than or equal to timestamp.
Less than timestamp.
Equal to timestamp.
Filter by transaction signature.
Get transactions with signatures greater than or equal to this value.
Get transactions after this signature.
Get transactions with signatures less than or equal to this value.
Get transactions before this signature.
Filter by transaction status.
succeededfailedany
Filter transactions for related token accounts. Controls whether to include transactions involving token accounts owned by the address.
nonebalanceChangedall
Narrows results to transactions where the queried address participated in a token transfer matching specific criteria. All fields are optional and combined with AND semantics.
Counterparty address. Matches transfers whose other side is this address.
Transfer direction relative to the queried address.
inoutany
Token mint to filter on.
Raw on-chain amount range filter. All fields are optional and can be combined.
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:
getTransactionsForAddress Example:
"getTransactionsForAddress"
Array containing the required account address and optional configuration object.
Example:
[
"Vote111111111111111111111111111111111111111",
{
"transactionDetails": "signatures",
"limit": 50,
"sortOrder": "desc",
"filters": {
"status": "succeeded",
"slot": { "gte": 1000, "lt": 2000 },
"tokenTransfer": {
"direction": "in",
"mint": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v"
}
}
}
]Previous
getTransfersByAddressQuery parsed, human-readable token and native SOL transfer objects by address with filters by mint, time, amount, counterparty, and pagination.
Next
getTransactionsForAddress