Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with a blockchain events API to retrieve detailed information about a specific blockchain event subscription using a unique reference ID. It is useful for users who want to monitor or audit blockchain event subscriptions by fetching their current status and details.

Typical use cases include:

  • Verifying the status and parameters of an existing blockchain event subscription.
  • Auditing event subscriptions for compliance or troubleshooting.
  • Integrating blockchain event data into workflows for alerting or further processing.

For example, a user might input the blockchain type, network, and a subscription reference ID to fetch the subscription's metadata and confirm it is active or to retrieve its configuration details.

Properties

Name Meaning
blockchain The blockchain network to query (e.g., Ethereum, Bitcoin).
network The specific network within the blockchain (e.g., mainnet, testnet).
referenceId The unique identifier of the blockchain event subscription to retrieve details for.
context Optional additional context string to pass along with the request (usage depends on API).

Output

The node outputs JSON data representing the details of the blockchain event subscription identified by the provided reference ID. This typically includes subscription metadata such as status, event types subscribed to, callback URLs, creation timestamps, and other relevant subscription attributes.

If the API supports binary data in responses (not evident here), the node would handle it accordingly, but this operation primarily returns structured JSON data.

Dependencies

  • Requires an API key credential for authenticating requests to the Crypto APIs REST API.
  • Relies on the Crypto APIs service endpoint defined in the bundled OpenAPI specification file (2024-12-12-final.json).
  • No additional external dependencies beyond standard n8n environment and the Crypto APIs credential.

Troubleshooting

  • Operation Not Found Error: If the specified operation is not found in the API spec, ensure the operation name matches exactly and that the node version is up to date with the latest API spec.
  • Missing Required Parameters: The blockchain, network, and referenceId fields are required. Omitting any will cause errors.
  • API Authentication Errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Network or API Errors: Check network connectivity and API service status if requests fail unexpectedly.
  • Invalid Reference ID: If the reference ID does not correspond to an existing subscription, the API may return an error or empty result.

Links and References

Discussion