Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation fetches detailed information about a specific blockchain block identified by its height, including all Unspent Transaction Outputs (UTXOs) associated with that block. It is useful for blockchain analysts, developers, or services that need to track the state of UTXOs at a particular block height, such as for auditing, wallet balance calculations, or transaction verification.

Practical examples include:

  • Retrieving all UTXOs for a Bitcoin block at height 700,000 to analyze spendable outputs.
  • Fetching UTXO details on an Ethereum-compatible blockchain at a given block height for reconciliation purposes.

Properties

Name Meaning
blockchain The blockchain network to query, e.g., Bitcoin, Ethereum, etc.
network The specific network environment, such as mainnet, testnet, or other supported networks.
blockHeight The numeric height of the block to retrieve details for.
context Optional additional context or metadata to pass along with the request.

Output

The output is a JSON array where each item represents data returned from the API call for the specified block height's UTXOs. Each JSON object contains detailed information about the block and its UTXOs as provided by the external Crypto APIs service.

If binary data were involved, it would be summarized here, but this operation returns only JSON data related to blockchain blocks and UTXOs.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Needs an API key credential configured in n8n to authenticate requests.
  • Relies on the external Crypto APIs service to provide blockchain data.
  • Uses internal helper functions to perform HTTP requests to the API.

Troubleshooting

  • Common issues:
    • Invalid or missing API credentials will cause authentication errors.
    • Providing an unsupported blockchain or network name may result in "Operation not found" or similar errors.
    • Incorrect block height values (e.g., negative numbers or heights beyond the current chain tip) can lead to empty results or errors.
  • Error messages:
    • "Operation <operationName> not found" indicates the requested operation is not recognized; verify the operation name and resource selection.
    • Network or API errors may occur if the Crypto APIs service is unreachable or rate limits are exceeded.
  • Resolutions:
    • Ensure API credentials are correctly set up and valid.
    • Double-check input parameters for correctness and supported values.
    • Handle errors gracefully using the node's "Continue On Fail" option if needed.

Links and References

Discussion