Standardized version of getTransactions
The account address to query. You can use any format: raw (0:abcd), base64 (EQ), or base64url (UQ). The API automatically detects and converts the format. A TON account address. Accepts raw format (workchain:hex like 0:abc...), base64 bounceable (EQ...), base64 non-bounceable (UQ...), or base64url. All formats are automatically detected.
Maximum number of transactions to return. The default is 10. For accounts with many transactions, use pagination (lt + hash) to fetch more.
Starting point for transaction history. Pass the lt from last_transaction_id to start from the most recent, or from a specific transaction to continue pagination.
Transaction hash to start from A 256-bit hash value. Accepts either hex format (64 characters) or base64 format (44 characters). Used for block hashes, transaction hashes, and cryptographic proofs.
Stop fetching when reaching this logical time. Use this to limit the time range of returned transactions. Set to 0 (default) to fetch all available history.
Request data from archival nodes. Regular nodes only keep recent history (about 2 days). Set to true when querying old transactions or historical state. Archival requests may be slower.
OK
Indicates if the request succeeded. If false, check the error field for details.
The response data. Only present when ok is true.
Optional request ID that you can pass in the request and receive back in the response. Useful for matching async responses.
JSON-RPC protocol version, always "2.0".
Request ID. Pass any string and it will be echoed in the response.