Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node integrates with a blockchain events API to monitor new confirmed token transactions and track each confirmation on a specified blockchain network. It is useful for applications that need real-time updates about token transfers, such as wallets, portfolio trackers, or alerting systems. For example, you can use this node to trigger workflows when a token transfer to a specific address is confirmed or when multiple confirmations occur, ensuring transaction finality before proceeding.

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 correlate or identify the callback context.
JSON Body A collection of optional parameters:
- address Specific wallet address to filter token transactions.
- allowDuplicates Boolean flag to allow duplicate notifications for the same transaction.
- callbackSecretKey Secret key used to secure callbacks from the API.
- callbackUrl URL where the API will send event notifications.
- confirmationsCount Number of confirmations to wait for before triggering the event.

Output

The node outputs an array of JSON objects representing the confirmed token transactions and their confirmations received from the blockchain events API. Each JSON object contains details about the token transaction event, such as transaction identifiers, addresses involved, amounts, and confirmation status.

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

Dependencies

  • Requires an API key credential for authenticating with the Crypto APIs service.
  • Needs proper configuration of the blockchain and network parameters matching supported values by the API.
  • If using callbacks, a publicly accessible callback URL must be provided.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node for operation metadata.

Troubleshooting

  • Operation not found error: This occurs if the selected operation does not match any in the bundled API spec. Ensure the "operation" parameter is correctly set to "New Confirmed Tokens Transactions And Each Confirmation".
  • Invalid blockchain or network: Using unsupported or misspelled blockchain/network names will cause API errors. Verify correct values.
  • Callback URL issues: If the callback URL is unreachable or misconfigured, events will not be delivered. Make sure the URL is publicly accessible and secured if needed.
  • Missing API credentials: The node requires a valid API key credential; missing or invalid keys will cause authentication failures.
  • AllowDuplicates flag: Misuse may lead to repeated events; understand its effect on event delivery.

Links and References

Discussion