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.
signatures: Basic signature info (faster)full: Complete transaction data (eliminates need for getTransaction calls, requires limit ≤ 100)desc: Newest first (default)asc: Oldest first (chronological, great for historical analysis)transactionDetails: "signatures"transactionDetails: "full""slot:position")finalized or confirmed. The processed commitment is not supported.gte, gt, lte, ltExample: { "slot": { "gte": 1000, "lte": 2000 } }gte, gt, lte, lt, eqExample: { "blockTime": { "gte": 1640995200, "lte": 1641081600 } }gte, gt, lte, ltExample: { "signature": { "lt": "SIGNATURE_STRING" } }succeeded: Only successful transactionsfailed: Only failed transactionsany: Both successful and failed (default){ "status": "succeeded" }none: Only return transactions that reference the provided address (default)balanceChanged: Return transactions that reference either the provided address or modify the balance of a token account owned by the provided address (recommended)all: Return transactions that reference either the provided address or any token account owned by the provided address{ "tokenAccounts": "balanceChanged" }transactionDetails: "full"). Same as getTransaction API. Options: json, jsonParsed, base64, base580 to include all versioned transactions.The JSON-RPC protocol version.
2.0 "2.0"
A unique identifier for the request.
"1"
The name of the RPC method to invoke.
getTransactionsForAddress "getTransactionsForAddress"
Array containing the required account address and optional configuration object.
[
"Vote111111111111111111111111111111111111111",
{
"transactionDetails": "signatures",
"limit": 50,
"sortOrder": "desc",
"filters": {
"status": "succeeded",
"slot": { "gte": 1000, "lt": 2000 }
}
}
]