Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with a cryptocurrency API to retrieve detailed information about a specific transaction's UTXOs (Unspent Transaction Outputs) by providing the transaction hash. It is useful for blockchain developers, analysts, or anyone needing to inspect the inputs and outputs of a particular crypto transaction on various blockchains.

Typical use cases include:

  • Verifying transaction details for auditing or compliance.
  • Tracking the flow of funds in a blockchain transaction.
  • Building wallet or explorer applications that display transaction data.

For example, you can input a Bitcoin transaction hash and get all UTXO details related to that transaction on the Bitcoin mainnet or testnet.

Properties

Name Meaning
blockchain The blockchain network to query, e.g., Bitcoin, Ethereum, etc.
network The specific network within the blockchain, such as "mainnet", "testnet", or others.
transactionHash The unique hash identifier of the transaction whose UTXO details are requested.
context Optional additional context string to pass along with the request (usage depends on API).

Output

The node outputs an array of JSON objects representing the UTXO details of the specified transaction. Each object contains structured data fields returned by the Crypto APIs service, typically including information such as input addresses, output addresses, amounts, confirmations, and other transaction metadata.

If the API supports binary data (e.g., raw transaction hex), it would be included accordingly, but this node primarily returns JSON-formatted transaction 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 external Crypto APIs service endpoint defined in the bundled OpenAPI specification file (2024-12-12-final.json).

Troubleshooting

  • Operation not found error: If the operation name does not match any known API operation, ensure the "Operation" property is correctly set to "Get Transaction Details By Transaction Hash UTXOs".
  • Invalid or missing parameters: Make sure all required properties (blockchain, network, transactionHash) are provided and valid.
  • API authentication errors: Verify that the API key credential is properly configured and has sufficient permissions.
  • Network or connectivity issues: Check internet access and Crypto APIs service status.
  • Unexpected API response: Inspect the error message returned in the output JSON; enabling "Continue On Fail" can help capture errors without stopping the workflow.

Links and References

Discussion