Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to retrieve detailed information about a specific XRP blockchain block by its block height. It is useful for users who want to fetch historical or current block data on the XRP ledger, such as developers building blockchain explorers, analytics dashboards, or monitoring tools.

A practical example: Given a particular block height on the XRP network, this node fetches all relevant details of that block, including transactions and metadata, enabling further processing or analysis within an n8n workflow.

Properties

Name Meaning
network The XRP network to query (e.g., mainnet, testnet).
blockHeight The height (number) of the XRP block to retrieve details for.
context Optional context string to correlate responses with requests (useful for tracking).

Output

The node outputs a JSON array where each item corresponds to the detailed data of the requested XRP block at the specified block height. The JSON structure includes comprehensive block information as provided by the Crypto APIs, such as block metadata, transaction list, timestamps, and other relevant blockchain data.

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 authenticating requests to Crypto APIs.
  • The node reads from a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically resolve API paths and parameters.

Troubleshooting

  • Common issues:

    • Incorrect or missing API key credential will cause authentication failures.
    • Providing an invalid or non-existent block height may result in errors or empty responses.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • Operation <operationName> not found: Indicates the internal operation identifier could not be matched; usually a configuration or version mismatch issue.
    • API errors returned from Crypto APIs (e.g., 404 Not Found if block height does not exist).
  • Resolutions:

    • Ensure the API key credential is correctly set up and has necessary permissions.
    • Verify the block height value is valid and exists on the selected XRP network.
    • Check network connectivity and retry.

Links and References

Discussion