Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to retrieve blockchain-related data. Specifically, for the "addresses-latest" resource and the "Get Address Balance XRP" operation, it fetches the balance of a given XRP (Ripple) address on a specified network.

Common scenarios where this node is beneficial include:

  • Monitoring XRP wallet balances in real-time.
  • Integrating XRP balance checks into automated workflows such as payment processing or portfolio tracking.
  • Building dashboards that display current XRP holdings.

For example, you can use this node to input an XRP address and network (like mainnet or testnet) and get back the current balance of that address.

Properties

Name Meaning
network The blockchain network to query (e.g., mainnet, testnet).
address The XRP wallet address whose balance you want to retrieve.
context Optional string to correlate or label the request context; useful for tracking calls.

Output

The node outputs JSON data representing the XRP address balance information returned by the Crypto APIs service. This typically includes fields such as the confirmed balance, unconfirmed balance, and possibly other metadata about the address state.

If the API returns binary data (not typical for this operation), it would be included accordingly, but for this operation, output is JSON only.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Needs an API key credential configured in n8n to authenticate requests.
  • The node reads from a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically build requests.

Troubleshooting

  • Operation not found error: If the node throws Operation ... not found, ensure the operation name matches exactly and the bundled OpenAPI spec file is present and correctly loaded.
  • Invalid network or address: Providing an incorrect network name or malformed XRP address will cause API errors. Validate inputs before running.
  • API authentication errors: Make sure the API key credential is set up properly in n8n and has sufficient permissions.
  • Continue on Fail: If enabled, errors per item are returned as JSON objects with an error field instead of stopping execution.

Links and References

Discussion