Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation "List Transactions by Address XRP" under the resource "addresses-latest" interacts with a cryptocurrency API to retrieve a list of XRP transactions associated with a specific wallet address. It is useful for users who want to monitor or analyze transaction history on the XRP ledger for a given address.

Typical use cases include:

  • Tracking incoming and outgoing payments for an XRP wallet.
  • Auditing transaction activity for compliance or accounting.
  • Building dashboards or alerts based on XRP transaction data.

For example, a user can input their XRP wallet address and specify filters such as transaction type or sorting order to get a tailored list of relevant transactions.

Properties

Name Meaning
network The blockchain network to query (e.g., mainnet, testnet).
address The XRP wallet address whose transactions are to be listed.
context Optional context string to correlate requests and responses.
limit Optional number to limit the maximum number of transactions returned.
sortingOrder Optional sorting order of the results (e.g., ascending or descending).
startingAfter Optional cursor for pagination to start listing after a specific transaction ID.
transactionType Optional filter to specify the type of XRP transactions to return. Possible values:
- account-set
- account-delete
- check-cancel
- check-cash
- check-create
- deposit-preauth
- escrow-cancel
- escrow-create
- escrow-finish
- offer-cancel
- offer-create
- payment
- payment-channel-claim
- payment-channel-create
- payment-channel-fund
- set-regular-key
- signer-list-set
- ticket-create
- trust-set

Output

The output is a JSON array where each element represents a transaction related to the specified XRP address. Each transaction object contains detailed information as provided by the Crypto APIs REST API, including but not limited to transaction identifiers, types, timestamps, amounts, and involved parties.

If binary data were returned (not indicated here), it would typically represent raw transaction payloads or cryptographic proofs, but this operation focuses on JSON transaction data.

Dependencies

  • Requires an active connection to the Crypto APIs REST API service.
  • Needs an API key credential configured in n8n to authenticate requests.
  • Uses the Crypto APIs endpoint corresponding to the XRP blockchain network.
  • Relies on internal helper functions to perform HTTP requests and handle pagination.

Troubleshooting

  • Common issues:

    • Invalid or missing XRP address format may cause errors or empty results.
    • Network parameter must match supported networks; otherwise, the API may reject the request.
    • Exceeding rate limits imposed by the Crypto APIs service can result in throttling errors.
    • Pagination parameters like startingAfter must correspond to valid transaction IDs from previous responses.

  • Error messages:

    • "Operation ... not found": Indicates a misconfiguration or unsupported operation name; ensure the correct operation is selected.
    • API errors related to authentication usually mean the API key is missing, invalid, or lacks required permissions.
    • Validation errors on parameters suggest incorrect input types or missing required fields.

To resolve these, verify all input parameters, ensure the API key is correctly set up, and consult the Crypto APIs documentation for valid values.

Links and References

Discussion