Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with a cryptocurrency API service to retrieve blockchain data. Specifically, the "List Transactions by Block Height UTXOs" operation fetches transactions associated with unspent transaction outputs (UTXOs) at a given block height on a specified blockchain network.

Use cases include:

  • Auditing or analyzing all transactions confirmed in a particular block.
  • Tracking UTXOs for wallet balance reconciliation or forensic analysis.
  • Building blockchain explorers or monitoring tools that require detailed block-level transaction data.

For example, you might use this node to list all transactions in Bitcoin mainnet block number 700000 to analyze spending patterns or verify transaction confirmations.

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 for which to list transactions by UTXOs.
context Optional string to provide additional context or metadata for the request.
limit Optional number to limit the number of returned transactions.
offset Optional number to specify the starting point for pagination in the result set.

Output

The node outputs an array of JSON objects representing transactions related to UTXOs at the specified block height. Each object corresponds to a transaction and contains detailed blockchain data fields as provided by the external API.

If binary data were involved (e.g., raw transaction hex), it would be included in a separate binary output field, but this operation focuses on JSON transaction data only.

Dependencies

  • Requires an active connection to the external Crypto APIs REST service.
  • Needs an API key credential configured in n8n to authenticate requests.
  • Relies on the presence of a local OpenAPI specification file (2024-12-12-final.json) bundled with the node for operation metadata and parameter mapping.
  • Uses standard Node.js modules fs and path for reading the specification file.

Troubleshooting

  • Operation Not Found Error: If the node throws an error stating the operation is not found, ensure the operation name matches exactly and the bundled OpenAPI spec file is present and correctly loaded.
  • Invalid Parameters: Missing or incorrect required parameters like blockchain, network, or blockHeight will cause API request failures. Double-check input values.
  • API Authentication Errors: Verify that the API key credential is properly configured and has sufficient permissions.
  • Rate Limits or Quotas: The external API may enforce rate limits; consider using limit and offset properties to paginate results and avoid hitting limits.
  • Network Issues: Connectivity problems between n8n and the external API can cause timeouts or errors; check network access and proxy settings if applicable.

Links and References

Discussion