Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation allows users to list Unspent Transaction Outputs (UTXOs) associated with an HD Wallet identified by an extended public key (xPub, yPub, or zPub). It supports multiple blockchains and networks, enabling retrieval of UTXO data for hierarchical deterministic wallets. This is useful in scenarios such as wallet auditing, balance reconciliation, transaction building, or blockchain analytics where detailed information about spendable outputs is required.

For example, a user managing a Bitcoin HD wallet can use this node to fetch all UTXOs on the Bitcoin mainnet for their xPub key, which can then be used to construct new transactions or monitor funds.

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 addresses.
network The specific network within the blockchain (e.g., mainnet, testnet).
context Optional context string for additional request scoping or metadata.
derivation Optional derivation method; options are account or bip32.
limit Optional number to limit the number of returned UTXOs.
offset Optional number to offset the start position of the returned UTXOs list.

Output

The output is a JSON array where each item represents a UTXO associated with the specified HD wallet. Each UTXO object typically includes details such as transaction ID, output index, amount, address, and confirmation status. This structured data enables further processing or integration into workflows.

The node does not output binary data.

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 API authentication setup.

Troubleshooting

  • Common issues:
    • Invalid or missing extended public key will cause the API request to fail.
    • Incorrect blockchain or network parameters may result in no data or errors.
    • Rate limits or API quota exceeded errors from the external service.
  • Error messages:
    • "Operation ... not found" indicates a misconfiguration or unsupported operation name internally.
    • Network or authentication errors usually stem from invalid API credentials or connectivity issues.
  • Resolutions:
    • Verify that the extended public key is correctly formatted and corresponds to the selected blockchain.
    • Confirm that the blockchain and network values match supported options.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Use the "Continue On Fail" option to handle partial failures gracefully.

Links and References

Discussion