Actions113
- blocks Actions
- Get Block Details By Block Hash UTXOs
- List Transactions by Block Hash EVM
- List Transactions by Block Hash UTXOs
- List Transactions By Block Hash XRP
- List Transactions By Block Height XRP
- List Transactions by Block Height EVM
- List Transactions by Block Height UTXOs
- Get Block Details By Block Height UTXOs
- Get Block Details By Block Height EVM
- Get Block Details By Block Height XRP
- Get Block Details By Block Hash EVM
- Get Block Details By Block Hash XRP
- Get Last Mined Block EVM
- Get Last Mined Block UTXOs
- Get Latest Mined Block XRP
- List Latest Mined Blocks UTXOs
- List Latest Mined Blocks EVM
- List Latest Mined Blocks XRP
- HD Wallets Actions
- Sync HD Wallet (xPub, yPub, zPub)
- Derive And Sync New Receiving Addresses UTXO
- Derive And Sync New Change Addresses UTXO
- Derive And Sync New Receiving Addresses EVM
- Derive And Sync New Receiving Addresses XRP
- List Synced Addresses UTXO
- List Synced Addresses EVM
- List Synced Addresses XRP
- List HD Wallet (xPub, yPub, zPub) Transactions UTXO
- List HD Wallet (xPub, yPub, zPub) Transactions EVM
- List HD Wallet (xPub, yPub, zPub) Transactions XRP
- List HD Wallet (xPub, yPub, zPub) UTXOs
- Prepare A UTXO-Based Transaction From HD Wallet (xPub, yPub, zPub)
- Prepare A Transaction From an Address in HD Wallet (xPub, yPub, zPub) EVM
- Get HD Wallet (xPub, yPub, zPub) Assets UTXO
- Get HD Wallet (xPub, yPub, zPub) Assets EVM
- Get HD Wallet (xPub, yPub, zPub) Assets XRP
- Get HD Wallet (xPub, yPub, zPub) Details UTXO
- Get HD Wallet (xPub, yPub, zPub) Details EVM
- Get HD Wallet (xPub, yPub, zPub) Details XRP
- List Synced HD Wallets (xPub, yPub, zPub)
- Activate HD Wallet (xPub, yPub, zPub)
- Delete Synced HD Wallet (xPub, yPub, zPub)
- address-latest Actions
- Utilities Actions
- simulate-transactions Actions
- addresses-latest Actions
- Get Address Balance Solana
- List Transactions By Address Solana
- Get Address Balance EVM
- Get Address Balance XRP
- Get Address Balance Kaspa
- List Confirmed Transactions By Address EVM
- List Transactions by Address XRP
- List Confirmed Transactions By Address UTXOs
- List Confirmed Transactions By Address Kaspa
- List Unconfirmed Transactions by Address UTXOs
- List Internal Transactions By Address EVM
- Get Next Available Nonce EVM
- List Confirmed Tokens Transfers By Address EVM
- addresses-historical Actions
- Get Address Balance UTXOs
- List Confirmed Transactions By Address EVM history
- List Confirmed Transactions By Address UTXO Historical
- List Unspent Transaction Outputs By Address UTXOs
- Sync Address
- List Synced Addresses
- Get Synced Address Tokens Transfer EVM
- Activate Synced Address
- Delete Synced Address
- List Synced Address Internal Transactions EVM
- List Tokens By Address Synced EVM
- blockchain-events Actions
- New Confirmed Coins Transactions
- New Unconfirmed Coins Transactions
- New Confirmed Tokens Transactions
- New Confirmed Coins Transactions And Each Confirmation
- New Confirmed Tokens Transactions And Each Confirmation
- Mined Transaction
- New Block
- List Blockchain Events Subscriptions
- Get Blockchain Event Subscription Details By Reference ID
- Delete Blockchain Event Subscription
- Activate Blockchain Event Subscription
- New Confirmed Internal Transactions
- New Confirmed Internal Transactions And Each Confirmation
- Crypto Transactions Actions
- Get Transaction Details By Transaction Hash Solana
- Get Transaction Details By Transaction Id Kaspa
- Get Transaction Details By Transaction Hash EVM
- Get Transaction Details By Transaction Hash UTXOs
- Get Transaction Details By Transaction Hash XRP
- List Internal Transaction Details by Transaction Hash EVM
- List Tokens Transfers By Transaction Hash EVM
- List Logs By Transaction Hash EVM
- Get Raw Transaction Data UTXOs
- contracts Actions
- blockchain-fees Actions
- broadcast-transactions Actions
- prepare-transactions Actions
- Market Data & Prices Actions
Overview
This node operation lists transactions for an HD Wallet (using extended public keys like xPub, yPub, or zPub) on the XRP blockchain network. It is useful for users who want to retrieve detailed transaction history associated with a hierarchical deterministic wallet without exposing private keys. Typical scenarios include auditing wallet activity, tracking incoming and outgoing payments, or integrating wallet transaction data into financial dashboards.
For example, a user managing multiple XRP wallets can use this node to fetch recent transactions by providing the extended public key and specifying pagination parameters such as limit and offset.
Properties
| Name | Meaning |
|---|---|
| blockchain | The blockchain network to query; here it should be set to "XRP" or relevant XRP network. |
| extendedPublicKey | The extended public key (xPub, yPub, zPub) of the HD Wallet whose transactions are listed. |
| network | The specific XRP network environment (e.g., mainnet, testnet) to target. |
| context | Optional context string to correlate requests or responses, often used for tracing. |
| derivation | The derivation method used for the HD wallet addresses; options: "account", "bip32". |
| limit | Optional number to limit how many transactions to return in one response (pagination). |
| offset | Optional number to skip a certain count of transactions before starting to return results (pagination). |
Output
The output is a JSON array where each element represents a transaction related to the specified HD Wallet on the XRP blockchain. Each transaction object typically contains details such as transaction ID, timestamp, amounts, involved addresses, and status.
If binary data were returned (not indicated here), it would represent raw transaction payloads or attachments, but this operation focuses on JSON transaction data only.
Dependencies
- Requires an API key credential for accessing the Crypto APIs REST API.
- The node depends on the Crypto APIs service to fetch blockchain data.
- No additional environment variables are explicitly required beyond the configured API authentication.
Troubleshooting
Common issues:
- Providing an invalid or malformed extended public key will result in errors or empty results.
- Incorrect blockchain or network values may cause the API to reject the request.
- Pagination parameters (limit, offset) must be numeric and within allowed ranges; otherwise, the API might return errors or unexpected results.
Error messages:
"Operation ... not found": Indicates the requested operation identifier does not exist in the API specification; usually a configuration or version mismatch.- API errors related to authentication failures suggest missing or invalid API credentials.
- Network or timeout errors indicate connectivity issues with the Crypto APIs service.
To resolve these, verify all input parameters, ensure valid API credentials are configured, and check network connectivity.