Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to retrieve detailed information about blockchain blocks, specifically fetching block details by a given block hash including its UTXOs (Unspent Transaction Outputs). It is useful in scenarios where users need to analyze or verify specific blocks on a blockchain network, such as for auditing transactions, tracking funds, or building blockchain explorers.

For example, a user might want to get all UTXO details of a Bitcoin block identified by its hash on the mainnet to understand which outputs are still spendable. This can help in wallet balance calculations or transaction history analysis.

Properties

Name Meaning
blockchain The blockchain network to query, e.g., Bitcoin, Ethereum, etc.
network The specific network within the blockchain, e.g., mainnet, testnet, ropsten, etc.
blockHash The unique hash identifier of the block whose details and UTXOs are to be retrieved.
context Optional context string to correlate responses with requests (useful for debugging).

Output

The output is a JSON array where each element contains detailed information about the specified block and its UTXOs. The structure typically includes fields describing the block metadata and an array of UTXOs associated with that block hash.

If binary data were involved (not indicated here), it would represent raw blockchain data or files, but this node focuses on JSON data representing blockchain block details.

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 bundled OpenAPI specification file (2024-12-12-final.json) for operation definitions.
  • Uses internal helper functions to perform HTTP requests to the Crypto APIs service.

Troubleshooting

  • Common issues:
    • Invalid or missing API key credential will cause authentication failures.
    • Incorrect blockHash value may result in "block not found" errors.
    • Specifying unsupported blockchain or network names can lead to request errors.
  • Error messages:
    • "Operation <operationName> not found" indicates a misconfiguration or outdated API spec; ensure the operation name matches supported operations.
    • Network or API errors will propagate from the Crypto APIs service; check connectivity and API status.
  • To resolve errors, verify input parameters, ensure valid credentials, and confirm the block hash exists on the specified blockchain and network.

Links and References

Discussion