Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node integrates with a Crypto APIs REST API to listen for new confirmed coin transactions and track each confirmation on a specified blockchain network. It is useful for applications that need real-time updates about cryptocurrency transactions, such as wallet monitoring, transaction auditing, or triggering workflows upon transaction confirmations.

For example, a user can configure this node to watch Bitcoin transactions on the mainnet and receive callbacks whenever a new transaction is confirmed or when additional confirmations occur, enabling automated processing or alerting based on transaction status.

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 context string to correlate or identify requests.
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 requests.
- callbackUrl URL to which the API will send callbacks for new confirmed transactions and confirmations.
- confirmationsCount Number of confirmations to wait for before triggering the event.

Output

The node outputs an array of JSON objects representing the data received from the Crypto APIs service about new confirmed coin transactions and their confirmations. Each JSON object contains detailed information about the transaction event.

If configured with a callback URL, the node effectively subscribes to webhook events, so the output corresponds to the payloads delivered by the external service.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node for operation metadata but does not require user interaction with it.

Troubleshooting

  • Operation Not Found Error: If the node throws an error stating the operation is not found, ensure the selected operation matches exactly "New Confirmed Coins Transactions And Each Confirmation" and that the bundled OpenAPI spec file is present and unmodified.
  • Missing Required Parameters: The blockchain and network properties are required. Omitting them will cause request failures.
  • Callback URL Issues: If using a callback URL, verify that the URL is publicly accessible and correctly configured to receive POST requests.
  • API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
  • Duplicate Notifications: If duplicates are received unexpectedly, check the allowDuplicates setting.

Links and References

Discussion