Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with a comprehensive Crypto APIs REST API, specifically targeting historical address data on blockchains. The "Get Synced Address Tokens Transfer EVM" operation retrieves token transfer events related to a specified Ethereum Virtual Machine (EVM) compatible address. This is useful for tracking token movements in and out of wallet addresses on various EVM blockchains.

Common scenarios include:

  • Monitoring token transfers for auditing or compliance.
  • Building dashboards that display token activity for specific addresses.
  • Integrating blockchain token transfer data into broader financial or analytics workflows.

For example, you could use this node to fetch the latest ERC-20 token transfers for a given Ethereum address on the Ethereum mainnet or any other supported EVM-compatible network.

Properties

Name Meaning
blockchain The blockchain network to query, e.g., Ethereum, Binance Smart Chain, Polygon, etc.
network The specific network within the blockchain, such as mainnet, testnet, or custom networks.
address The wallet address whose token transfer history you want to retrieve.
context Optional context string to correlate requests or responses (e.g., for pagination).
limit Optional number to limit the number of returned token transfer records.
sortingOrder Optional order to sort results, typically ascending or descending by timestamp or block.
startingAfter Optional cursor for pagination to start fetching results after a specific record ID.

Output

The node outputs an array of JSON objects representing token transfer events associated with the specified address. Each object typically includes details such as:

  • Token information (e.g., token symbol, contract address).
  • Transfer details (e.g., from address, to address, amount).
  • Blockchain metadata (e.g., block number, transaction hash, timestamp).

If binary data were involved (not indicated here), it would represent raw blockchain data or files, but this operation focuses on JSON-formatted token transfer records.

Dependencies

  • Requires an active connection to the Crypto APIs REST API service.
  • Needs an API key credential configured in n8n to authenticate requests.
  • No additional external dependencies beyond standard Node.js modules and the Crypto APIs service.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Incorrect blockchain or network names may result in "Operation not found" or empty results.
    • Providing an invalid wallet address format can lead to request failures.
    • Pagination parameters like startingAfter must be used carefully to avoid skipping or repeating data.
  • Error messages:

    • "Operation <operationName> not found" indicates a misconfiguration or typo in the operation name.
    • API errors related to rate limits or invalid parameters will be returned in the error message field.

To resolve these:

  • Verify API credentials are correctly set up.
  • Double-check property values for correctness.
  • Use the optional limit and pagination properties to manage large datasets efficiently.

Links and References

Discussion