Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with a comprehensive Crypto APIs REST API to retrieve historical blockchain data. Specifically, for the "addresses-historical" resource and the "List Confirmed Transactions By Address EVM history" operation, it fetches confirmed transaction records associated with a given Ethereum Virtual Machine (EVM) compatible address on a specified blockchain network.

This node is beneficial when you want to analyze or monitor past confirmed transactions of a wallet address on blockchains like Ethereum or other EVM-compatible chains. For example, it can be used in portfolio tracking, auditing wallet activity, or integrating blockchain transaction histories into financial applications.

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, testnet).
address The wallet address whose confirmed transactions are to be listed.
context Optional context string to correlate responses with requests (for tracking purposes).
limit Optional number to limit the number of returned transactions.
sortingOrder Optional order to sort the results (e.g., ascending or descending by block/time).
startingAfter Optional cursor for pagination to start listing after a specific transaction ID.

Output

The node outputs an array of JSON objects representing confirmed transactions related to the specified address on the chosen EVM-compatible blockchain network. Each object contains detailed transaction data as provided by the Crypto APIs service, such as transaction hashes, block numbers, timestamps, sender and receiver addresses, amounts, and status confirmations.

If binary data were involved (not indicated here), it would typically represent raw transaction payloads or related files, but this operation focuses on JSON transaction data only.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Needs an API key credential configured in n8n to authenticate requests.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically build request parameters and paths.
  • No additional external dependencies beyond standard Node.js modules and the Crypto APIs service.

Troubleshooting

  • Common Issues:

    • Incorrect or missing blockchain/network/address parameters will cause the API call to fail or return no data.
    • Pagination parameters like startingAfter must correspond to valid transaction IDs; otherwise, the response may be empty or error out.
    • API rate limits or invalid API keys will result in authentication errors.
  • Error Messages:

    • "Operation <operationName> not found": Indicates the requested operation is not defined in the API spec or was misspelled.
    • Network or authentication errors from the Crypto APIs service will propagate and should be checked against your API key validity and network connectivity.
  • Resolution Tips:

    • Verify all required parameters are correctly set.
    • Ensure your API key credential is valid and has sufficient permissions.
    • Use the optional context parameter to help trace and debug requests.
    • Handle pagination carefully using limit and startingAfter.

Links and References

Discussion