Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with a blockchain events API to list subscriptions for blockchain event notifications. It allows users to retrieve information about existing blockchain event subscriptions filtered by blockchain type, network, and optionally context, with support for pagination through limit and offset parameters.

Common scenarios include:

  • Monitoring which blockchain event subscriptions are active on a given blockchain and network.
  • Auditing or managing event subscriptions programmatically.
  • Integrating blockchain event subscription data into workflows for alerting or analytics.

For example, a user might list all event subscriptions on the Ethereum mainnet to verify which smart contract events are being tracked.

Properties

Name Meaning
blockchain The blockchain network to query (e.g., Ethereum, Bitcoin).
network The specific network within the blockchain (e.g., mainnet, testnet).
context Optional context string to filter subscriptions by a specific context or environment.
limit Optional number to limit the number of returned subscriptions (pagination).
offset Optional number to skip a certain number of subscriptions (pagination offset).

Output

The output is an array of JSON objects representing blockchain event subscriptions. Each object contains details about a single subscription as returned by the external API.

If the node encounters errors during execution and "Continue On Fail" is enabled, it outputs JSON objects containing an error field with the error message.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the Crypto APIs REST API.
  • Uses an internal helper function to make HTTP requests to the API endpoints.
  • Reads a local OpenAPI specification JSON file (2024-12-12-final.json) to dynamically resolve API paths and operations.

Troubleshooting

  • Operation not found error: If the specified operation cannot be found in the API spec, ensure the operation name matches exactly and that the node version supports it.
  • Missing required parameters: The blockchain and network properties are required; missing these will cause request failures.
  • API authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
  • Pagination issues: Using invalid values for limit or offset may result in empty or incomplete results.
  • Network or connectivity errors: Ensure the n8n instance can reach the external API endpoint.

Links and References

Discussion