Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node activates an HD Wallet (Hierarchical Deterministic Wallet) using an extended public key format such as xPub, yPub, or zPub on a specified blockchain network. It is useful for users who want to register or enable their HD wallets within a crypto API platform to start tracking addresses and transactions derived from the wallet's extended public key.

Common scenarios include:

  • Integrating wallet management into automated workflows.
  • Activating HD wallets for monitoring balances and transactions without exposing private keys.
  • Managing multiple blockchain networks and wallet types programmatically.

For example, a user can activate an HD wallet on the Bitcoin blockchain by providing the xPub key and network type, enabling subsequent operations like address generation or transaction tracking.

Properties

Name Meaning
blockchain The blockchain network where the HD wallet will be activated (e.g., Bitcoin, Ethereum).
extendedPublicKey The extended public key (xPub, yPub, zPub) representing the HD wallet to activate.
network The specific network type within the blockchain (e.g., mainnet, testnet).
context Optional additional context or metadata related to the activation request.
JSON Body Additional optional parameters provided as a JSON collection to customize the request.

Output

The node outputs a JSON array containing the response from the Crypto APIs service after attempting to activate the HD wallet. The structure of each JSON object corresponds to the API's response schema for the activation operation, typically including details about the wallet status, identifiers, and any relevant metadata.

No binary data output is produced by this node.

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) bundled with the node to resolve API paths and operations.
  • Network connectivity to the Crypto APIs service endpoint is necessary.

Troubleshooting

  • Operation Not Found Error: If the node throws an error stating the operation was not found, ensure that the "Activate HD Wallet (xPub, yPub, zPub)" operation is correctly selected and that the bundled OpenAPI spec file is intact.
  • Invalid Parameters: Missing or incorrect values for required properties like blockchain, extendedPublicKey, or network may cause API errors. Verify all required fields are properly filled.
  • API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
  • Network Issues: Connectivity problems to the Crypto APIs service will result in request failures; check your internet connection and firewall settings.

Links and References

Discussion