Returns transaction history for an account in a standardized format. Transactions are returned newest-first. Each transaction includes the triggering inbound message, all outbound messages, and fees paid. The response includes a previous_transaction_id cursor for paginating through older transactions.
The account address to query.
Account address in raw format (e.g., 0:ca6e321c...) or user-friendly format (e.g., EQDKbjIcfM...). 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.
SHA-256 transaction hash to start pagination 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 keep at least the last 2 days of history. Set to true when querying old transactions or historical state. Archival requests may be slower.
Returns transactions in standardized format with a pagination cursor.
Returns true if the request succeeded; otherwise false. See the error field for details.
The method return value. The structure depends on the method called; see individual method documentation for response schemas. 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 identifier.
Echoed request identifier from the original JSON-RPC request.