Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to retrieve historical UTXO (Unspent Transaction Outputs) balance information for a specific blockchain address. The "Get Address Balance UTXOs" operation fetches detailed data about the unspent outputs associated with an address on a given blockchain network.

Typical use cases include:

  • Wallet management applications that need to display or calculate spendable balances.
  • Blockchain explorers showing detailed transaction output states.
  • Auditing tools verifying address balances at historical points in time.
  • Services aggregating UTXO data for analytics or reporting.

For example, a user can input a Bitcoin address and specify the Bitcoin mainnet network to get all unspent outputs currently available for that address, which is essential for constructing new transactions.

Properties

Name Meaning
blockchain The blockchain to query, e.g., Bitcoin, Ethereum, etc.
network The specific network of the blockchain, such as mainnet, testnet, ropsten, etc.
address The wallet address whose UTXO balance is being requested.
context Optional additional context parameter to refine or specify the request further.

Output

The node outputs an array of JSON objects representing the UTXOs for the specified address. Each object typically contains details such as:

  • Transaction IDs
  • Output indices
  • Amounts
  • Confirmations
  • Script types
  • Other metadata related to each unspent output

If the API supports binary data (e.g., raw transaction hex), it would be included accordingly, but this node primarily returns structured JSON data describing UTXOs.

Dependencies

  • Requires an active connection to the Crypto APIs service via an API key credential configured in n8n.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically configure operations and parameters.
  • No other external dependencies are required beyond standard Node.js modules and the Crypto APIs service.

Troubleshooting

  • Operation not found error: If the specified operation is not recognized, ensure the operation name matches exactly and that the node version supports it.
  • Invalid or missing parameters: Make sure all required properties (blockchain, network, address) are provided and correctly formatted.
  • API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network issues: Connectivity problems to the Crypto APIs endpoint may cause timeouts or failures.
  • Empty or unexpected results: Confirm the address exists on the specified blockchain and network, and that it has unspent outputs.

Links and References

Discussion