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 transactions by a specific EVM (Ethereum Virtual Machine) address. It is useful for blockchain developers, analysts, or enthusiasts who want to retrieve transaction history related to an Ethereum-compatible address on various blockchains and networks.

Typical use cases include:

  • Monitoring wallet activity by fetching confirmed transactions.
  • Auditing or analyzing transaction flows for a given address.
  • Integrating blockchain data into dashboards or automated workflows.

For example, you can specify the blockchain (e.g., Ethereum), network (e.g., mainnet), and an address to get a list of all confirmed transactions associated with that address, optionally controlling pagination and sorting.

Properties

Name Meaning
blockchain The blockchain to query (e.g., Ethereum, Binance Smart Chain).
network The specific network within the blockchain (e.g., mainnet, testnet).
address The EVM-compatible wallet address for which to list confirmed transactions.
context Optional context string to correlate responses with requests (useful for tracking).
limit Optional number to limit the maximum number of transactions returned.
sortingOrder Optional order to sort the results (e.g., ascending or descending).
startingAfter Optional cursor for pagination to start listing after a specific transaction ID or token.

Output

The node outputs a JSON array where each item represents a confirmed transaction related to the specified address. Each transaction object contains details such as transaction hash, block number, timestamp, sender and receiver addresses, value transferred, and other relevant blockchain transaction metadata.

If the API supports binary data (not indicated here), it would typically represent raw transaction data or receipts, but this node primarily returns structured JSON data about transactions.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Needs an API key credential configured in n8n for authentication.
  • No additional external dependencies beyond the Crypto APIs service.

Troubleshooting

  • Common issues:

    • Invalid or missing blockchain/network/address parameters will cause errors.
    • API rate limits may be hit if too many requests are made in a short time.
    • Pagination parameters like startingAfter must be used correctly to avoid empty results.
  • Error messages:

    • "Operation ... not found": Indicates the requested operation is not recognized; ensure correct operation name is selected.
    • Network or authentication errors: Verify API key credentials and network connectivity.
    • Parameter validation errors: Check that required fields like blockchain, network, and address are provided and valid.

Links and References

Discussion