Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation synchronizes an HD Wallet using its extended public key (xPub, yPub, or zPub) on a specified blockchain network. It interacts with a cryptocurrency API to fetch and update wallet data based on the provided extended public key and network details.

Common scenarios where this node is beneficial include:

  • Tracking balances and transactions of hierarchical deterministic wallets without exposing private keys.
  • Integrating wallet synchronization into automated workflows for portfolio management or auditing.
  • Fetching up-to-date wallet information for reporting or alerting systems.

For example, a user can input an xPub key from their Bitcoin wallet along with the network type (mainnet or testnet) to retrieve all associated addresses and transaction history, keeping their application in sync with the blockchain state.

Properties

Name Meaning
blockchain The blockchain network to query (e.g., Bitcoin, Ethereum).
extendedPublicKey The extended public key (xPub, yPub, or zPub) of the HD Wallet to synchronize.
network The specific network environment (e.g., mainnet, testnet) for the blockchain.
context Optional additional context parameter for the request (usage depends on API specifics).
JSON Body Additional optional parameters as a JSON collection to customize the API request body.

Output

The node outputs a JSON array containing the synchronized wallet data returned by the API. This typically includes wallet addresses, balances, transaction histories, and other relevant metadata associated with the HD Wallet.

If the API supports binary data output (not indicated here), it would be summarized accordingly, but this node primarily deals with JSON data representing wallet synchronization results.

Dependencies

  • Requires an active connection to a cryptocurrency API service that supports HD Wallet synchronization via extended public keys.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • Uses internal helper functions to perform HTTP requests to the API endpoints.
  • Reads a local OpenAPI specification 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 the API spec file is present and correctly loaded.
  • Invalid or missing parameters: Make sure required properties like blockchain, extendedPublicKey, and network are provided and valid.
  • API authentication errors: Verify that the API key or token credential is correctly set up in n8n and has sufficient permissions.
  • Network or connectivity issues: Confirm that the n8n instance can reach the external API endpoint without firewall or proxy restrictions.
  • Unexpected API response: Check if the API has changed or if additional required parameters need to be added in the JSON Body property.

Links and References

Discussion