Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation retrieves detailed information about an HD Wallet (Hierarchical Deterministic Wallet) for the XRP blockchain using an extended public key (xPub, yPub, or zPub). It is useful when you want to query wallet details such as addresses and balances derived from a given extended public key on the XRP network.

Common scenarios include:

  • Monitoring wallet activity without exposing private keys.
  • Integrating XRP wallet data into dashboards or reporting tools.
  • Auditing or tracking funds associated with a specific HD wallet.

Example: Given an extended public key for an XRP HD wallet, this node fetches its details on the specified XRP network (e.g., mainnet or testnet).

Properties

Name Meaning
blockchain The blockchain to query. For this operation, it should be set to "xrp" or relevant XRP identifier.
extendedPublicKey The extended public key (xPub, yPub, or zPub) of the HD wallet whose details are requested.
network The XRP network to use, e.g., "mainnet", "testnet", or other supported XRP networks.
context (Optional) Additional context string to correlate requests or responses.
derivation (Optional) The derivation method used by the HD wallet. Options: account or bip32.

Output

The output is a JSON array where each item contains the detailed information about the HD wallet corresponding to the provided extended public key on the XRP network. The structure typically includes wallet metadata, derived addresses, balances, transaction history, and other relevant wallet details.

If the node supports binary data output (not indicated here), it would represent any associated files or raw data related to the wallet, but this operation primarily returns structured JSON data.

Dependencies

  • Requires an active connection to the Crypto APIs REST API service.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node for operation definitions.
  • No additional external dependencies beyond the Crypto APIs service and standard Node.js modules.

Troubleshooting

  • Operation Not Found Error: If the node throws an error like Operation ... not found, ensure that the selected operation name matches exactly and that the bundled OpenAPI spec file is present and correctly loaded.
  • Invalid Extended Public Key: Providing an incorrect or malformed extended public key will result in API errors. Verify the key format before running.
  • Network Mismatch: Using an unsupported or incorrect network value may cause the API to reject the request. Confirm the network parameter matches the XRP environment you intend to query.
  • API Authentication Errors: Ensure the API key credential is valid and has permissions to access HD wallet endpoints.
  • Continue On Fail Behavior: If enabled, errors per item will be returned as JSON objects with an error field instead of stopping execution.

Links and References

Discussion