Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation fetches detailed information about a specific XRP cryptocurrency transaction by its transaction hash. It interacts with a blockchain data API to retrieve the transaction details on the XRP network.

Common scenarios where this node is useful include:

  • Verifying the status and details of an XRP transaction for auditing or reconciliation.
  • Tracking payments or transfers made on the XRP ledger.
  • Integrating XRP transaction data into workflows for reporting or alerting.

For example, a user can input a transaction hash and specify the XRP network (e.g., mainnet or testnet) to get comprehensive details such as transaction amount, sender, receiver, timestamp, and confirmation status.

Properties

Name Meaning
network The XRP network to query. This could be mainnet, testnet, or other supported XRP networks.
transactionHash The unique hash identifier of the XRP transaction to retrieve details for.
context Optional additional context string that can be used to correlate requests or responses.

Output

The output is a JSON array where each item contains detailed information about the XRP transaction corresponding to the provided transaction hash. The structure typically includes fields such as transaction ID, block height, timestamp, involved addresses, amounts, fees, and status.

No binary data output is produced by this operation.

Dependencies

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

Troubleshooting

  • Operation not found error: If the specified operation cannot be found in the API spec, ensure the operation name matches exactly and the node version is up to date.
  • Invalid or missing transaction hash: Make sure the transactionHash property is correctly set and corresponds to a valid XRP transaction.
  • Network parameter issues: Verify that the network value is correct and supported by the API.
  • API authentication errors: Confirm that the API key credential is properly configured and has sufficient permissions.
  • Continue on Fail: If enabled, errors will be returned as JSON objects with an error field instead of stopping execution.

Links and References

Discussion