Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation "List Synced Addresses UTXO" under the "HD Wallets" resource interacts with a cryptocurrency API to retrieve a list of Unspent Transaction Outputs (UTXOs) for addresses that have been synced from a Hierarchical Deterministic (HD) wallet. It is useful for blockchain developers, wallet providers, or crypto services that need to track available spendable outputs on wallet addresses derived from an extended public key.

Typical use cases include:

  • Displaying all unspent outputs for a user's HD wallet addresses.
  • Preparing inputs for new transactions by listing available UTXOs.
  • Auditing or monitoring wallet balances and transaction history at the address level.

For example, a wallet app could use this operation to fetch all UTXOs for addresses generated from a given extended public key on a specific blockchain network, filtering by address type or change status.

Properties

Name Meaning
blockchain The blockchain network to query (e.g., Bitcoin, Ethereum).
extendedPublicKey The extended public key (xpub) of the HD wallet to derive addresses from.
network The specific network environment (e.g., mainnet, testnet) for the blockchain.
context Optional context string to correlate requests or responses.
addressFormat Format of the addresses to list UTXOs for. Options: p2pkh, p2wpkh, p2pkh-cash.
isChangeAddress Boolean flag to filter addresses by whether they are change addresses (true/false).
limit Optional number to limit the number of returned UTXOs.
offset Optional number to skip a certain number of UTXOs before starting to return results.

Output

The output JSON array contains objects representing UTXOs associated with the synced addresses of the HD wallet. Each object typically includes details such as:

  • Address information (address string, format).
  • UTXO specifics (transaction id, output index, amount, confirmations).
  • Metadata related to the blockchain and network queried.

If binary data were involved (e.g., raw transaction hex), it would be summarized accordingly, but this operation focuses on JSON data describing UTXOs.

Dependencies

  • Requires an active connection to the Crypto APIs REST API service.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • Relies on the bundled OpenAPI specification file (2024-12-12-final.json) for endpoint definitions.
  • Uses internal helper functions to perform HTTP requests to the Crypto APIs endpoints.

Troubleshooting

  • Common issues:
    • Invalid or missing extended public key can cause errors or empty results.
    • Incorrect blockchain or network parameters may lead to no data or API errors.
    • Rate limits or API quota exceeded errors if too many requests are made.
  • Error messages:
    • "Operation <name> not found" indicates a misconfiguration or unsupported operation name.
    • Network or authentication errors suggest checking API credentials and connectivity.
  • Resolutions:
    • Verify all required parameters are correctly set.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Use optional parameters like limit and offset to paginate large result sets.

Links and References

Discussion