Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation "List Synced Addresses XRP" under the "HD Wallets" resource interacts with a Crypto APIs REST API to retrieve a list of synchronized Ripple (XRP) wallet addresses derived from an extended public key. It is useful for users who manage hierarchical deterministic (HD) wallets and want to programmatically fetch all XRP addresses that have been synced or generated on the blockchain network.

Typical use cases include:

  • Wallet management applications needing to display or audit all XRP addresses linked to a specific HD wallet.
  • Blockchain explorers or portfolio trackers that aggregate address data from an HD wallet.
  • Automated systems that monitor multiple XRP addresses for transactions or balances.

Properties

Name Meaning
blockchain The blockchain network to query, e.g., "ripple".
extendedPublicKey The extended public key (xpub) of the HD wallet to list synced addresses for.
network The specific network environment, such as "mainnet" or "testnet".
context Optional context string to correlate requests and responses for tracking purposes.
addressFormat Format of the returned addresses; currently supports "classic" format for XRP addresses.
isChangeAddress Boolean flag indicating whether to filter for change addresses only.
limit Maximum number of addresses to return in one response (pagination).
offset Number of addresses to skip before starting to collect the result set (pagination).

Output

The output is a JSON array where each element represents a synced XRP address associated with the provided extended public key. Each item typically includes details such as the address itself and possibly metadata like its derivation path or usage type (e.g., change or external).

If binary data were involved (not indicated here), it would represent raw blockchain or wallet data, but this operation focuses on JSON-formatted address information.

Dependencies

  • Requires an active connection to the Crypto APIs REST API service.
  • Needs a valid API authentication token configured in n8n credentials to authorize requests.
  • Relies on the Crypto APIs endpoint corresponding to HD Wallets and XRP blockchain data.
  • Uses local JSON schema files bundled with the node for operation definitions.

Troubleshooting

  • Common issues:

    • Missing or invalid extended public key will cause the API request to fail.
    • Incorrect blockchain or network parameters may lead to no results or errors.
    • Pagination parameters (limit, offset) must be numeric and within allowed ranges.
    • If the API key credential is not set or expired, authentication errors will occur.
  • Error messages:

    • "Operation ... not found": Indicates the requested operation identifier does not exist in the API specification; usually a configuration or version mismatch.
    • API errors related to invalid parameters or unauthorized access will be returned as error messages in the node output if "Continue On Fail" is enabled.

To resolve errors:

  • Verify all required parameters are correctly set.
  • Ensure the API key credential is valid and has necessary permissions.
  • Check the blockchain and network values against supported options.
  • Use pagination parameters carefully to avoid out-of-range requests.

Links and References

Discussion