> For the complete documentation index, see [llms.txt](https://apis.rightrev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apis.rightrev.com/rightrev-rest-api/platform/error-transactions.md).

# Error Transactions

The Error Transactions Details feature is powered by a single API endpoint. This endpoint supports multiple actions, each controlled through specific filters in the payload. Depending on the selected filter, the API will return the corresponding dataset.

This design allows you to interact with various parts of the Error Transactions using one consistent endpoint while simply adjusting the request filters.

<table><thead><tr><th width="62">#</th><th width="250">Functionality/ Fetaure</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td><a href="/rightrev-rest-api/platform/error-transactions/retrieve-error-transactions.md">Retrieve Error Transactions</a></td><td>This API retrieves a filtered list of remediable or discarded error transactions (orders, invoices, events, or MJEs) based on the criteria provided in the request payload.</td></tr><tr><td>2</td><td><a href="/rightrev-rest-api/platform/error-transactions/reprocess-error-transactions.md">Reprocess Error Transactions</a></td><td>This API Reprocess the Remediable orders/invoices/events transactions rejected by the system due to some exceptions</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://apis.rightrev.com/rightrev-rest-api/platform/error-transactions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.