Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to manage HD Wallets, specifically allowing users to delete a synced HD Wallet identified by its extended public key (xPub, yPub, or zPub). This operation is useful when you want to stop tracking or syncing a particular HD Wallet on a specified blockchain and network.

Common scenarios include:

  • Removing an HD Wallet from your system after it is no longer needed.
  • Cleaning up wallet data to reduce clutter or avoid unnecessary API calls.
  • Managing multiple wallets across different blockchains and networks by selectively deleting them.

For example, if you have synced an HD Wallet for Bitcoin mainnet using its xPub and want to remove it, this node operation will perform that deletion via the Crypto APIs service.

Properties

Name Meaning
blockchain The blockchain network where the HD Wallet exists (e.g., Bitcoin, Ethereum).
extendedPublicKey The extended public key (xPub, yPub, or zPub) of the HD Wallet to be deleted.
network The specific network within the blockchain (e.g., mainnet, testnet).
context Optional context string to provide additional information or metadata for the request.

Output

The node outputs a JSON array containing the response from the Crypto APIs service after attempting to delete the specified HD Wallet. The exact structure depends on the API's response but typically includes confirmation of deletion or error details.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically resolve API paths and parameters.

Troubleshooting

  • Operation not found error: If the node throws an error stating the operation was not found, ensure the "Delete Synced HD Wallet (xPub, yPub, zPub)" operation is correctly selected and the bundled OpenAPI spec file is intact.
  • Missing required parameters: The blockchain, extendedPublicKey, and network properties are mandatory. Omitting any will cause the request to fail.
  • API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network or connectivity issues: Ensure the n8n instance can reach the Crypto APIs endpoint without firewall or proxy restrictions.
  • Invalid extended public key: Providing an incorrect or malformed xPub/yPub/zPub may result in API errors; double-check the key format.

Links and References

Discussion