Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to list XRP transactions by a specific block height on a chosen network. It is useful for blockchain analysts, developers, or enthusiasts who want to retrieve detailed transaction data from the XRP ledger at a particular block height.

Practical examples include:

  • Auditing all transactions included in a specific XRP block.
  • Monitoring transaction activity at certain points in the XRP blockchain.
  • Integrating XRP transaction data into dashboards or analytics tools.

Properties

Name Meaning
network The XRP network to query (e.g., mainnet, testnet).
blockHeight The height (number) of the XRP block for which to list transactions.
context Optional context string to correlate responses with requests (useful for tracking).
limit Optional number to limit how many transactions are returned in the response.
offset Optional number to specify the starting point within the list of transactions (pagination).

Output

The node outputs an array of JSON objects representing XRP transactions found at the specified block height. Each object contains detailed transaction data as provided by the Crypto APIs service.

If binary data were involved, it would be summarized here, but this operation returns only JSON transaction data.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Needs an API key credential configured in n8n for authentication.
  • No additional environment variables are required beyond the API key setup.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication errors.
    • Providing an invalid blockHeight or network may result in no data or errors.
    • Exceeding rate limits imposed by the Crypto APIs service can cause request failures.
  • Error messages:

    • "Operation ... not found": Indicates the requested operation identifier was not recognized internally; usually a configuration or version mismatch.
    • Network or API errors will typically return messages from the Crypto APIs service; ensure correct parameters and valid credentials.
  • Resolutions:

    • Verify API key is correctly set up and has necessary permissions.
    • Double-check input parameters for correctness.
    • Use optional limit and offset parameters to paginate large result sets.
    • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion