Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node activates a blockchain event subscription using the Crypto APIs REST API. It allows users to subscribe to specific blockchain events on a chosen blockchain and network, identified by a reference ID. This is useful for applications that need to react to blockchain events such as transactions, token transfers, or other on-chain activities in real-time.

Practical examples include:

  • Monitoring wallet addresses for incoming or outgoing transactions.
  • Triggering workflows when a new block is added to a blockchain.
  • Receiving notifications about token transfers or smart contract events.

Properties

Name Meaning
blockchain The blockchain network to monitor (e.g., Ethereum, Bitcoin).
network The specific network of the blockchain (e.g., mainnet, testnet).
referenceId A unique identifier for the subscription reference.
context Optional additional context information for the subscription.
JSON Body Additional parameters for the subscription request, provided as a collection of fields.

Output

The node outputs an array of JSON objects representing the response from the Crypto APIs service after activating the blockchain event subscription. Each output item corresponds to the API's response data structure, typically including details about the subscription status and metadata.

If the API returns binary data (not indicated here), it would be included accordingly, but this operation primarily deals with JSON responses.

Dependencies

  • Requires an active API key credential for the Crypto APIs REST API.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) to dynamically resolve API paths and operations.
  • Network connectivity to the Crypto APIs service endpoint is necessary.

Troubleshooting

  • Operation not found error: If the specified operation cannot be found in the API specification, ensure the operation name matches exactly and the API spec file is present and correctly loaded.
  • Invalid or missing parameters: Make sure all required properties (blockchain, network, referenceId) are provided and valid.
  • API authentication errors: Verify that the API key credential is configured properly in n8n.
  • Network issues: Check internet connectivity and firewall settings if requests fail to reach the Crypto APIs service.
  • Continue on Fail: If enabled, errors will be returned as JSON objects with an error field instead of stopping execution.

Links and References

Discussion