Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation retrieves detailed Unspent Transaction Output (UTXO) information for a Hierarchical Deterministic (HD) Wallet identified by an extended public key (xPub, yPub, or zPub). It supports multiple blockchains and networks, allowing users to query the current UTXO state of their HD wallets. This is useful for cryptocurrency wallet management, auditing, or building applications that need to track spendable outputs associated with HD wallets.

Practical examples include:

  • Fetching all unspent outputs for a Bitcoin HD wallet on the mainnet.
  • Querying UTXOs for an Ethereum-compatible blockchain HD wallet.
  • Integrating UTXO data into portfolio trackers or payment processors.

Properties

Name Meaning
blockchain The blockchain network to query (e.g., Bitcoin, Ethereum).
extendedPublicKey The HD wallet's extended public key (xPub, yPub, or zPub) identifying the wallet.
network The specific network within the blockchain (e.g., mainnet, testnet).
context Optional context string to specify additional request context or metadata.
derivation Optional derivation method used; can be either "account" or "bip32".

Output

The output is a JSON array where each item represents details about the UTXOs associated with the specified HD wallet. Each JSON object contains the relevant UTXO data returned from the Crypto APIs REST API, such as transaction IDs, output indices, amounts, and addresses.

If binary data were involved, it would typically represent raw transaction data or similar, but this operation focuses on JSON-formatted UTXO details only.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • 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 to dynamically resolve API paths and parameters.

Troubleshooting

  • Common issues:
    • Invalid or malformed extended public key may cause errors or empty results.
    • Incorrect blockchain or network selection can lead to no data found or API errors.
    • Missing or invalid API credentials will result in authentication failures.
  • Error messages:
    • Operation <operationName> not found: Indicates the requested operation is not defined in the API spec; ensure correct operation name is selected.
    • API request errors usually return descriptive messages from the Crypto APIs service; verify input parameters and credentials.
  • To resolve errors, double-check all required properties, ensure valid API credentials are set up, and confirm the extended public key corresponds to the chosen blockchain and network.

Links and References

Discussion