Crypto APIs

Overview

This node interacts with the Crypto APIs REST API to retrieve detailed information about HD Wallets (Hierarchical Deterministic Wallets) specifically for EVM-compatible blockchains using extended public keys such as xPub, yPub, or zPub. It is useful when you want to fetch wallet details like addresses and balances derived from an extended public key without exposing private keys.

Common scenarios include:

• Monitoring wallet activity on Ethereum or other EVM chains.
• Integrating wallet data into dashboards or analytics tools.
• Verifying wallet derivation paths and network-specific details.

For example, a user can input an Ethereum xPub key and get all associated wallet details on the Ethereum mainnet or testnets.

Properties

Output

The node outputs a JSON array where each item contains detailed information about the HD Wallet corresponding to the provided extended public key on the specified blockchain and network. The exact structure depends on the API response but typically includes:

• Wallet addresses derived from the extended public key.
• Balance and transaction summaries.
• Metadata related to the derivation path and network.
• Possibly additional wallet attributes as returned by the Crypto APIs.

No binary data output is produced by this node.

Dependencies

• Requires an active connection to the Crypto APIs REST API.
• Needs an API authentication token configured in n8n credentials to authorize requests.
• Relies on the Crypto APIs OpenAPI specification file (2024-12-12-final.json) bundled with the node for operation definitions.

Troubleshooting

• Operation Not Found Error: If the node throws an error stating the operation was not found, ensure that the selected Resource and Operation match exactly and that the bundled OpenAPI spec file is intact.
• Invalid Extended Public Key: Providing an incorrectly formatted or unsupported extended public key will result in API errors. Verify the key format before use.
• Network or Blockchain Mismatch: Ensure the blockchain and network parameters correspond correctly; otherwise, the API may return empty or error responses.
• API Authentication Issues: Missing or invalid API credentials will cause authentication failures. Confirm that the API key credential is properly set up in n8n.
• Continue On Fail Behavior: If enabled, the node will output error messages in the JSON output instead of stopping execution, which helps in batch processing scenarios.

Links and References

• Crypto APIs Documentation
• HD Wallets Explained
• EVM Chains Overview