Crypto APIs

Overview

This node operation fetches the assets associated with an HD Wallet (using extended public keys such as xPub, yPub, or zPub) on EVM-compatible blockchains. It queries blockchain data APIs to retrieve detailed asset information for a given HD wallet's extended public key on a specified blockchain and network.

Common scenarios where this node is beneficial include:

• Portfolio tracking applications that need to aggregate all assets held by an HD wallet.
• Blockchain analytics tools analyzing wallet holdings across multiple networks.
• Crypto tax software gathering wallet asset data for reporting.
• Wallet management dashboards displaying token balances and NFTs for hierarchical deterministic wallets.

Practical example: Given an Ethereum mainnet xPub key, the node can return all ERC-20 tokens, NFTs, and native ETH balance associated with that wallet’s derived addresses.

Properties

Output

The output is a JSON array where each element represents an asset associated with the HD wallet on the specified blockchain and network. Each JSON object typically contains details such as:

• Asset type (native coin, token, NFT)
• Asset identifier (contract address or token ID)
• Balance or quantity held
• Metadata related to the asset (name, symbol, decimals)
• Possibly other blockchain-specific asset details

If binary data is returned (not typical for this operation), it would represent raw asset metadata or media linked to NFTs.

Dependencies

• Requires access to a Crypto APIs REST API service that provides blockchain data endpoints.
• Needs an API authentication token configured in n8n credentials to authorize requests.
• No additional external dependencies beyond standard Node.js modules and the Crypto APIs service.

Troubleshooting

• Common issues:

  • Invalid or malformed extended public key input causing API errors.
  • Unsupported blockchain or network values leading to "operation not found" or empty results.
  • Missing or incorrect API credentials resulting in authentication failures.
  • Network connectivity problems preventing API calls.

• Error messages:

  • "Operation <operationName> not found": Indicates the requested operation is not defined in the API specification or the node parameters are misconfigured. Verify the operation name and resource selection.
  • API response errors related to invalid parameters usually mean one of the required inputs (blockchain, extendedPublicKey, network) is missing or incorrect.
  • Authentication errors suggest checking the configured API key credential.

• Resolutions:

  • Double-check all required input properties for correctness.
  • Ensure the API key credential is valid and has necessary permissions.
  • Confirm the blockchain and network names match supported values by the API.
  • Use the optional context and derivation fields only if you understand their impact on the request.

Links and References

• Crypto APIs Documentation
• HD Wallets and Extended Public Keys Explained
• EVM-compatible Blockchains Overview