Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to retrieve blockchain-related data. Specifically, for the "addresses-latest" resource and the "Get Address Balance EVM" operation, it fetches the balance of a given Ethereum Virtual Machine (EVM) compatible address on a specified blockchain network.

Common scenarios where this node is beneficial include:

  • Monitoring wallet balances on various EVM-compatible blockchains.
  • Building dashboards or alerts based on wallet balance changes.
  • Integrating blockchain wallet data into broader workflows or applications.

For example, you can use this node to get the current balance of an Ethereum address on the Ethereum mainnet or any other supported EVM chain by specifying the blockchain, network, and address parameters.

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 wallet address whose balance you want to retrieve.
context Optional additional context parameter for the request (usage depends on API specifics).

Output

The node outputs JSON data representing the balance information of the specified address on the chosen blockchain and network. The exact structure depends on the API response but typically includes fields such as:

  • The address queried.
  • The balance amount in the native token.
  • Possibly metadata like timestamp or block number.

If the API supports binary data output, it would be summarized here; however, this node primarily returns JSON data.

Dependencies

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

Troubleshooting

  • Operation not found error: If the specified operation is not recognized, ensure that the operation name matches exactly and that the node version supports it.
  • Invalid address or network: Providing an incorrect blockchain, network, or address may result in errors or empty responses. Verify these inputs carefully.
  • API authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Rate limiting or quota exceeded: Crypto APIs may limit request rates; handle such errors by implementing retries or backoff strategies.
  • Missing required parameters: All required properties must be provided; missing them will cause the node to fail.

Links and References

Discussion