Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with a cryptocurrency API service to retrieve raw transaction data, specifically the UTXOs (Unspent Transaction Outputs) for a given transaction hash on a specified blockchain and network. It is useful in scenarios where users need detailed information about the inputs and outputs of a crypto transaction, such as for wallet auditing, transaction analysis, or blockchain explorers.

For example, a user might want to fetch all UTXOs related to a Bitcoin transaction on the mainnet to verify which outputs are still spendable.

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.
transactionHash The hash identifier of the transaction whose raw UTXO data is to be retrieved.
context Optional additional context string that can be used for tracking or metadata purposes.

Output

The node outputs an array of JSON objects representing the raw transaction data related to the UTXOs of the specified transaction. Each object contains detailed information returned by the external Crypto APIs service, typically including fields such as transaction inputs, outputs, amounts, addresses, and status.

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

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Requires an API key credential configured in n8n to authenticate requests.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically build request parameters and endpoints.
  • Uses internal helper functions to perform HTTP requests to the Crypto APIs service.

Troubleshooting

  • Operation Not Found Error: If the node throws an error stating the operation was not found, ensure the "operation" parameter is correctly set to "Get Raw Transaction Data UTXOs" and that the bundled OpenAPI spec file is present and unmodified.
  • Invalid Parameters: Missing or incorrect values for blockchain, network, or transactionHash will cause API errors. Verify these inputs carefully.
  • API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
  • Network Issues: Connectivity problems to the Crypto APIs service will result in request failures; check internet access and firewall settings.
  • Continue On Fail: If enabled, the node will output error messages in the JSON output instead of stopping execution, useful for batch processing.

Links and References

Discussion