Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation "List Transactions By Block Hash XRP" under the "blocks" resource interacts with a cryptocurrency API to retrieve a list of transactions associated with a specific XRP blockchain block identified by its hash. It is useful for users who want to analyze or monitor all transactions included in a particular XRP ledger block.

Common scenarios include:

  • Auditing or verifying transactions within a given XRP block.
  • Fetching transaction data for analytics or reporting purposes.
  • Integrating XRP blockchain data into workflows that require transaction details by block.

For example, a user might input a known XRP block hash and receive all transactions confirmed in that block, enabling further processing or storage.

Properties

Name Meaning
network The XRP network to query (e.g., mainnet, testnet).
blockHash The unique hash identifier of the XRP block whose transactions are to be listed.
context Optional context string to correlate responses with requests (useful for pagination).
limit Optional number to limit the maximum number of transactions returned in the response.
offset Optional number to specify the starting point in the list of transactions (pagination).

Output

The node outputs a JSON array where each element represents a transaction found in the specified XRP block. Each transaction object contains detailed information as provided by the underlying Crypto APIs service, such as transaction identifiers, amounts, sender and receiver addresses, timestamps, and other relevant metadata.

If binary data were involved (not indicated here), it would typically represent raw transaction payloads or related files, but this operation focuses on JSON transaction data only.

Dependencies

  • Requires an active connection to the Crypto APIs REST API service.
  • Needs a valid API authentication token configured in n8n credentials to authorize requests.
  • Relies on the Crypto APIs endpoint corresponding to XRP blockchain data.

Troubleshooting

  • Operation Not Found Error: If the node throws an error stating the operation is not found, ensure the operation name matches exactly and the bundled API specification file is correctly loaded.
  • Invalid or Missing Parameters: Errors may occur if required parameters like network or blockHash are missing or invalid. Double-check these inputs.
  • API Authentication Failures: Ensure the API key credential is properly set up and has sufficient permissions.
  • Rate Limits or Quotas: The external API may enforce rate limits; consider adding delays or handling retries.
  • Empty Results: If no transactions are returned, verify the block hash exists on the specified network and that it contains transactions.

Links and References

Discussion