Crypto APIs

Overview

This node operation fetches detailed information about a specific Ethereum Virtual Machine (EVM) blockchain transaction by its transaction hash. It is useful for users who want to retrieve comprehensive data on a particular crypto transaction, such as status, block confirmations, sender and receiver addresses, gas used, and other metadata related to the transaction.

Common scenarios include:

• Verifying the status of a transaction submitted to an EVM-compatible blockchain.
• Auditing or tracking transactions for wallets or smart contracts.
• Integrating blockchain transaction details into workflows for reporting or alerting.

For example, a user can input a transaction hash from the Ethereum mainnet and get back all relevant details about that transaction, including whether it was successful, how much gas was consumed, and timestamps.

Properties

Output

The output is a JSON array where each item contains detailed information about the requested transaction. The structure typically includes fields such as:

• Transaction hash
• Block number and timestamp
• Sender and recipient addresses
• Gas price and gas used
• Transaction status (success/failure)
• Input data and logs (if any)

If the node supports binary data output, it would represent any associated raw transaction data or receipts, but this operation primarily returns structured JSON data describing the transaction.

Dependencies

• Requires an API key credential for accessing the Crypto APIs REST API service.
• The node depends on the Crypto APIs service endpoint and requires proper configuration of the API authentication in n8n.
• No additional external dependencies beyond the bundled Crypto APIs SDK and standard Node.js modules.

Troubleshooting

• Common issues:

  • Invalid or missing transaction hash will result in errors or empty responses.
  • Incorrect blockchain or network parameters may cause the API to return "not found" or similar errors.
  • Network connectivity or API quota limits could lead to request failures.

• Error messages:

  • Operation <operationName> not found: Indicates a misconfiguration or unsupported operation name; ensure the correct operation is selected.
  • API errors returned from the Crypto APIs service usually include descriptive messages; verify the input parameters and API credentials.

• Resolution tips:

  • Double-check the transaction hash format and correctness.
  • Confirm the blockchain and network values match the transaction's actual chain.
  • Ensure the API key credential is valid and has sufficient permissions.
  • Use the "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

• Crypto APIs Documentation
• Ethereum Transaction Structure
• n8n Documentation