Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to list confirmed token transfers by a specific blockchain address on an EVM-compatible network. It is useful for users who want to track token movements related to a wallet address, such as monitoring incoming or outgoing ERC-20 or other token transfers on Ethereum or similar blockchains.

Practical examples include:

  • Tracking all confirmed token transfers for a given wallet address on Ethereum mainnet.
  • Monitoring token activity on test networks or alternative EVM chains.
  • Building dashboards or alerts based on token transfer events involving specific addresses.

Properties

Name Meaning
blockchain The blockchain network to query (e.g., Ethereum, Binance Smart Chain).
network The specific network within the blockchain (e.g., mainnet, ropsten).
address The wallet address whose confirmed token transfers you want to list.
context Optional context string to correlate requests and responses.
limit Optional number to limit the number of returned token transfer records.
sortingOrder Optional order to sort results, e.g., ascending or descending.
startingAfter Optional cursor for pagination to start listing after a specific item.

Output

The node outputs a JSON array where each element represents a confirmed token transfer related to the specified address. Each JSON object contains details about the token transfer event, such as token information, sender and receiver addresses, transaction hashes, timestamps, and amounts transferred.

If binary data were involved (not indicated here), it would typically represent files or media associated with the token or transaction, but this node focuses on JSON data describing token transfers.

Dependencies

  • Requires an API key credential for Crypto APIs REST API configured in n8n.
  • No additional external dependencies beyond the Crypto APIs service.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node for operation metadata.

Troubleshooting

  • Operation not found error: If the node throws an error stating the operation was not found, ensure that the selected Resource and Operation are correct and supported by the installed version of the node.
  • Invalid or missing parameters: Required parameters like blockchain, network, and address must be provided; missing these will cause errors.
  • API authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Rate limiting or quota exceeded: Crypto APIs may enforce rate limits; handle such errors by implementing retries or increasing quota.
  • Pagination issues: When using startingAfter for pagination, ensure the value corresponds to a valid cursor from previous results.

Links and References

Discussion