Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node provides an interface to interact with various blockchain-related utilities via the Crypto APIs REST API. Specifically, for the "Utilities" resource and the "Decode X-Address" operation, it decodes a given X-Address (a specific type of address format used in some blockchains) into its underlying components.

Common scenarios where this node is beneficial include:

  • Converting encoded blockchain addresses into their standard form for further processing.
  • Validating and extracting information from complex address formats.
  • Integrating blockchain address decoding into automated workflows, such as wallet management or transaction monitoring.

For example, a user might input an X-Address from the Ripple blockchain and decode it to obtain the classic address and tag, which can then be used in other nodes or systems.

Properties

Name Meaning
blockchain The blockchain network to use (e.g., Ripple, Bitcoin).
network The specific network environment (e.g., mainnet, testnet) on the selected blockchain.
xAddress The X-Address string that needs to be decoded.
context Optional additional context information related to the decoding operation.

Output

The node outputs a JSON array where each item contains the decoded details of the provided X-Address. This typically includes fields such as the classic address, destination tag, and any other relevant decoded data depending on the blockchain.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Crypto APIs REST API service.
  • Needs an API key credential configured in n8n to authenticate 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

  • Common issues:

    • Invalid or malformed X-Address input may cause errors or unexpected results.
    • Incorrect blockchain or network selection can lead to failed API calls or incorrect decoding.
    • Missing or invalid API authentication credentials will prevent successful requests.
  • Error messages:

    • Operation <operationName> not found: Indicates the requested operation is not defined in the API spec; ensure the correct operation name is selected.
    • API request failures often return error messages from the Crypto APIs service; verify the input parameters and credentials.
  • Resolutions:

    • Double-check the X-Address format and correctness.
    • Confirm the blockchain and network values match the intended environment.
    • Ensure the API key credential is properly set up and has necessary permissions.

Links and References

Discussion