Crypto APIs

Overview

This node operation "List Tokens Transfers By Transaction Hash EVM" under the "Crypto Transactions" resource allows users to retrieve a list of token transfer events associated with a specific Ethereum Virtual Machine (EVM) transaction hash. It queries blockchain data for tokens transferred during that transaction, which is useful for tracking token movements, auditing transactions, or analyzing token activity on EVM-compatible blockchains.

Practical examples include:

• Fetching all ERC-20 or ERC-721 token transfers triggered by a particular transaction.
• Auditing token transfers for compliance or accounting purposes.
• Building dashboards or alerts based on token transfer activity within a transaction.

Properties

Output

The output is a JSON array where each item represents a token transfer event related to the specified transaction hash. Each JSON object typically contains details such as:

• Token contract address
• Sender and receiver addresses
• Amount of tokens transferred
• Token type (e.g., ERC-20, ERC-721)
• Additional metadata about the transfer event

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

Dependencies

• Requires an API key credential for accessing the Crypto APIs REST API service.
• The node depends on the external Crypto APIs service to fetch blockchain data.
• No additional environment variables are explicitly required beyond the API authentication setup in n8n.

Troubleshooting

• Common issues:

  • Invalid or missing transaction hash: Ensure the transaction hash is correct and corresponds to a transaction on the specified blockchain and network.
  • Network or blockchain mismatch: Verify that the selected blockchain and network match the transaction hash's origin.
  • API rate limits or quota exceeded: The external API may throttle requests; consider adding delays or upgrading your plan.

• Error messages:

  • Operation <operationName> not found: This indicates an internal misconfiguration or unsupported operation; ensure the node version and API spec are up to date.
  • Errors related to invalid parameters usually mean required fields like blockchain, network, or transactionHash are missing or malformed.
  • Network errors or timeouts suggest connectivity issues with the Crypto APIs service.

Resolving these generally involves verifying input parameters, checking API credentials, and ensuring network connectivity.

Links and References

• Crypto APIs Documentation
• Ethereum Transaction Hash Explanation
• ERC-20 Token Standard
• ERC-721 Token Standard