> For the complete documentation index, see [llms.txt](https://retailcloud.gitbook.io/portals/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://retailcloud.gitbook.io/portals/central-administration-server-cas/reports/listings/transaction-id/coupon-list.md).

# Coupon List

### **Overview**

Go to **CAS** --> **Reports** --> **Listings** --> **Transaction ID**

Listing provide basic information which is useful for creating import files and getting a general summary of the transaction type, such as reviewing Coupon start and end times and the frequencies in which they repeat.

![](/files/-LxPCtxiLDCsAupfHL3-)

\
**Id:** The ID number of the coupon

**Name:** The name of the coupon

**Type:** The type of coupon

**Amount:** the amount of the coupon

**Repeat Frequency:** The frequency that the coupon repeats

**Start Date:** The day the coupon starts on.&#x20;

**End Date:** The day the coupon ends on.&#x20;

**End time:** The time the coupon ends. <br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://retailcloud.gitbook.io/portals/central-administration-server-cas/reports/listings/transaction-id/coupon-list.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
