Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with a cryptocurrency API service to list synced Hierarchical Deterministic (HD) wallets identified by extended public keys (xPub, yPub, zPub). It allows users to retrieve information about HD wallets that have been synchronized on a specified blockchain and network. This is useful for applications that need to monitor or manage multiple wallet addresses derived from a single master key without exposing private keys.

Common scenarios include:

  • Tracking balances and transactions across all addresses generated from an HD wallet.
  • Auditing or reporting on wallet activity for accounting or compliance.
  • Integrating wallet data into dashboards or analytics platforms.

For example, a user can specify the blockchain as Bitcoin, the network as mainnet, and then list all synced HD wallets associated with their account or API key.

Properties

Name Meaning
blockchain The blockchain network to query (e.g., Bitcoin, Ethereum).
network The specific network within the blockchain (e.g., mainnet, testnet).
context Optional context string to filter or specify additional request context.
limit Optional number to limit the number of returned HD wallets in the response.
offset Optional number to skip a certain number of results, used for pagination.

Output

The node outputs an array of JSON objects representing the synced HD wallets matching the query parameters. Each object contains details about an individual HD wallet, such as its extended public key and related metadata provided by the API.

If the API supports binary data output for this operation (not indicated here), it would typically represent files or raw data related to the wallets, but this node focuses on JSON data.

Dependencies

  • Requires an active connection to the external Crypto APIs REST API service.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • Uses the Crypto APIs OpenAPI specification file (2024-12-12-final.json) bundled with the node for operation definitions.
  • No other external dependencies are required.

Troubleshooting

  • Operation Not Found Error: If the node throws an error stating the operation was not found, ensure the selected operation matches exactly "List Synced HD Wallets (xPub, yPub, zPub)" and that the resource is set to "HD Wallets".
  • Missing Required Parameters: The blockchain and network properties are required. Omitting them will cause errors or empty responses.
  • API Authentication Errors: Verify that the API key or token is correctly configured and has sufficient permissions.
  • Pagination Issues: If too many results are returned, use the limit and offset properties to paginate through the data.
  • Empty Results: Confirm that there are actually synced HD wallets for the specified blockchain and network under your account.

Links and References

Discussion