Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node integrates with the Crypto APIs REST API to listen for new unconfirmed coin transactions on a specified blockchain and network. It is useful for applications that need real-time notifications or processing of incoming cryptocurrency transactions before they are confirmed on the blockchain. For example, a wallet service could use this node to update user balances immediately when an unconfirmed transaction is detected, or a monitoring system could trigger alerts for suspicious activity.

Properties

Name Meaning
blockchain The blockchain to monitor (e.g., Bitcoin, Ethereum).
network The specific network of the blockchain (e.g., mainnet, testnet).
context Optional string to correlate callback notifications with your internal context or workflow.
JSON Body A collection of optional parameters:
- address Specific wallet address to filter transactions for.
- allowDuplicates Boolean flag to allow duplicate notifications.
- callbackSecretKey Secret key used to secure callback notifications.
- callbackUrl URL to which the webhook notifications will be sent.

Output

The node outputs an array of JSON objects representing the data received from the Crypto APIs about new unconfirmed coin transactions. Each JSON object contains details about the transaction event as provided by the API. The node does not output binary data.

Dependencies

  • Requires an API key credential for Crypto APIs to authenticate requests.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically configure operations and parameters.
  • Network connectivity to Crypto APIs REST endpoints is necessary.

Troubleshooting

  • Operation Not Found Error: If the operation parameter is incorrect or missing, the node throws an error indicating the operation was not found. Ensure the "New Unconfirmed Coins Transactions" operation is selected correctly.
  • Missing Required Parameters: The blockchain and network properties are required. Omitting them will cause errors.
  • Callback URL Issues: If using the callbackUrl property, ensure the URL is reachable and properly configured to receive webhook calls.
  • API Authentication Failures: Verify that the API key credential is valid and has appropriate permissions.
  • Duplicate Notifications: If duplicates are received unexpectedly, check the allowDuplicates setting.

Links and References

Discussion