Crypto APIs

Overview

This node interacts with the Crypto APIs REST API to manage blockchain event subscriptions. Specifically, the "Delete Blockchain Event Subscription" operation allows users to delete an existing subscription for blockchain events on a specified blockchain and network by providing a unique reference ID. This is useful in scenarios where you want to stop receiving notifications or data related to certain blockchain events, such as transaction confirmations or address activity.

Practical examples include:

• Removing a webhook subscription that tracks new transactions on a specific blockchain network.
• Cleaning up unused or outdated event subscriptions to reduce unnecessary API calls or notifications.

Properties

Output

The node outputs a JSON array containing the response from the Crypto APIs after attempting to delete the blockchain event subscription. The structure typically includes confirmation of the deletion or error details if the operation failed.

No binary data output is produced by this operation.

Example output JSON snippet:

[
  {
    "status": "success",
    "message": "Subscription deleted successfully",
    "referenceId": "your-reference-id"
  }
]

If an error occurs, the output will contain an error field describing the issue.

Dependencies

• Requires an active connection to the Crypto APIs REST API.
• Needs an API key credential configured in n8n for authentication.
• The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically resolve API paths and parameters.

Troubleshooting

• Common issues:

  • Providing an incorrect or non-existent referenceId will result in an error indicating the subscription was not found.
  • Missing required parameters (blockchain, network, or referenceId) will cause validation errors before the API call.
  • Network connectivity problems or invalid API credentials will lead to authentication or connection errors.

• Error messages:

  • "Operation <operationName> not found": Indicates the internal mapping to the API operation failed; usually a node version mismatch or corrupted installation.
  • API errors returned from Crypto APIs are passed through; check the message for details like invalid parameters or permission issues.

• Resolution tips:

  • Double-check all required input fields.
  • Verify your API key credential is valid and has necessary permissions.
  • Ensure the referenced subscription exists before attempting deletion.

Links and References

• Crypto APIs Documentation
• Crypto APIs Webhooks Guide
• n8n Documentation on Creating Custom Nodes