> 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/transactions-ingestion/transaction-ingestion-order-invoices-events-and-bulk-uploads.md).

# Transaction Ingestion (Order, Invoices, Events & Bulk Uploads)

The Transaction upload feature is powered by a single API endpoint. This endpoint supports multiple actions, each controlled through specific parameters/objects. Depending on the selected action, the API will return the corresponding dataset.

This design allows you to interact with various transaction upload via CSV file or JSON using one consistent endpoint while simply adjusting the request parameters/objects.

<table><thead><tr><th width="58.0909423828125">#</th><th>Functionality/ Fetaure</th><th width="392.9090576171875">Description</th></tr></thead><tbody><tr><td>1</td><td><a href="/rightrev-rest-api/transactions-ingestion/transaction-ingestion-order-invoices-events-and-bulk-uploads/retrieve-file-data-csv-file.md">Retrieve file data - CSV file</a></td><td>This API is to get the uploaded orders/invoices/events/ All Bulk Uploads file data</td></tr><tr><td>2</td><td><a href="/rightrev-rest-api/transactions-ingestion/transaction-ingestion-order-invoices-events-and-bulk-uploads/retrieve-file-data-json-file.md">Retrieve file data - JSON file</a></td><td>This API is to get the uploaded orders/invoices/events file data in JSON format</td></tr><tr><td>3</td><td><a href="/rightrev-rest-api/transactions-ingestion/transaction-ingestion-order-invoices-events-and-bulk-uploads/retrieve-file-data-api-calls.md">Retrieve file data - API Calls</a></td><td>This API is to get the uploaded orders/invoices/events file data via API Calls</td></tr><tr><td>4</td><td><a href="/rightrev-rest-api/transactions-ingestion/transaction-ingestion-order-invoices-events-and-bulk-uploads/retrieve-uploaded-csv-file.md">Retrieve uploaded CSV File</a></td><td>This API is to download the uploaded orders/invoices/events data into CSV file</td></tr><tr><td>5</td><td><a href="/rightrev-rest-api/transactions-ingestion/transaction-ingestion-order-invoices-events-and-bulk-uploads/orders-invoices-events-transaction-ingestion-via-csv-file.md">Orders/Invoices/Events Transaction Ingestion via CSV file</a></td><td>This API is to upload and collect Orders/Invoices/Events data in CSV file format</td></tr><tr><td>6</td><td><a href="/rightrev-rest-api/transactions-ingestion/transaction-ingestion-order-invoices-events-and-bulk-uploads/order-ingestion-via-json-file.md">Order Ingestion via JSON file</a></td><td>This API is to upload and collect Orders data in JSON file format</td></tr><tr><td>7</td><td><a href="/rightrev-rest-api/transactions-ingestion/transaction-ingestion-order-invoices-events-and-bulk-uploads/invoice-ingestion-via-json-file.md">Invoice Ingestion via JSON file</a></td><td>This API is to upload and collect Invoices data in JSON file format</td></tr><tr><td>8</td><td><a href="/rightrev-rest-api/transactions-ingestion/transaction-ingestion-order-invoices-events-and-bulk-uploads/events-ingestion-via-json-file.md">Events Ingestion via JSON file</a></td><td>This API is to upload and collect Events data in JSON file format</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/transactions-ingestion/transaction-ingestion-order-invoices-events-and-bulk-uploads.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.