Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node provides an interface to validate cryptocurrency wallet addresses across various blockchains and networks using the Crypto APIs REST API. It is useful for developers or automation workflows that need to verify if a given address is valid before performing transactions, monitoring, or analytics.

Typical use cases include:

  • Ensuring user-inputted wallet addresses are correct before sending funds.
  • Validating addresses in batch processing pipelines.
  • Integrating address validation into crypto-related applications or services.

For example, you can input a blockchain type (e.g., Ethereum), specify the network (e.g., mainnet or testnet), and provide the wallet address to check if it is valid.

Properties

Name Meaning
blockchain The blockchain on which the address exists (e.g., Bitcoin, Ethereum).
network The specific network of the blockchain (e.g., mainnet, testnet).
context Optional context string to correlate requests with your system or logs.
JSON Body A collection of additional parameters:
- address The wallet address string to be validated.

Output

The node outputs a JSON array where each item corresponds to the response from the Crypto APIs address validation endpoint. The JSON structure typically includes details about the validity of the address and possibly metadata returned by the API.

If the node encounters errors during execution and "Continue On Fail" is enabled, it outputs an object with an error field containing the error message.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Needs an API key credential configured in n8n for authentication.
  • Relies on the external Crypto APIs service to perform address validation.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing unsupported blockchain or network values may result in errors or empty responses.
    • Incorrectly formatted wallet addresses will be flagged as invalid by the API.
  • Error messages:

    • "Operation <operationName> not found": Indicates the requested operation is not defined; ensure the operation name matches exactly.
    • API request errors due to network issues or invalid parameters will be surfaced as error messages in the node output.
  • Resolutions:

    • Verify API credentials and permissions.
    • Double-check blockchain and network inputs against supported values.
    • Validate address format before sending or handle errors gracefully.

Links and References

Discussion