Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node integrates with a blockchain events API to listen for new confirmed token transactions on specified blockchains and networks. It is useful for applications that need to react in real-time or near-real-time to token transfers, such as monitoring wallet activity, triggering alerts, updating dashboards, or automating workflows based on token movements.

For example, you could use this node to:

  • Track incoming token transactions to a specific wallet address.
  • Trigger notifications when tokens are received on a particular blockchain network.
  • Automate accounting or auditing processes by capturing token transfer events as they confirm on the blockchain.

Properties

Name Meaning
blockchain The blockchain network to monitor (e.g., Ethereum, Bitcoin).
network The specific network within the blockchain (e.g., mainnet, testnet).
context Optional string to pass additional context information with the request.
JSON Body A collection of optional parameters:
- address Wallet address to filter token transactions for.
- allowDuplicates Boolean flag to allow duplicate event callbacks.
- callbackSecretKey Secret key used to verify callbacks from the API.
- callbackUrl URL to receive webhook callbacks for new confirmed token transactions.
- receiveCallbackOn Numeric value indicating when to receive callbacks (e.g., on confirmation count).

Output

The node outputs an array of JSON objects representing new confirmed token transactions matching the specified criteria. Each object contains details about the transaction as returned by the blockchain events API, such as token details, sender and receiver addresses, amounts, transaction hashes, timestamps, and other relevant metadata.

If configured to receive webhook callbacks, the node can also handle incoming data via the callback URL, which will be processed similarly.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Crypto APIs service.
  • Needs access to the Crypto APIs REST endpoint.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node for operation definitions.
  • No additional external dependencies beyond the Crypto APIs service and standard n8n environment.

Troubleshooting

  • Operation not found error: If the specified operation is not recognized, ensure the "operation" property matches one of the supported operations exactly.
  • Missing required parameters: The blockchain and network properties are mandatory; missing these will cause errors.
  • API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Webhook callback issues: If using callbackUrl, ensure the URL is publicly accessible and correctly configured to receive POST requests.
  • Duplicate events: If duplicates are received, consider setting the allowDuplicates flag appropriately.
  • Network or connectivity problems: Check internet connection and API service status if requests fail.

Links and References

Discussion