> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/partner-api-reference/reference/promo-codes-exception-lists/models.md).

# Models

## The PromoCodeExceptionList object

```json
{"openapi":"3.1.0","info":{"title":"Partner Promo Code Exception Lists API","version":"16"},"components":{"schemas":{"PromoCodeExceptionList":{"type":"object","properties":{"Id":{"type":"string","description":"Unique identifier for the promo code exception list."},"Name":{"type":"string","description":"Display name of the promo code exception list."},"State":{"type":"string","enum":["ACTIVE","CLOSED","DEACTIVATED"],"description":"The current state of the promo code exception list."},"CampaignId":{"type":"string","description":"Unique identifier for the program this promo code exception list applies to."},"CreatedDate":{"type":"string","format":"date-time","description":"Date and time the promo code exception list was created (ISO 8601)."},"DeactivationDate":{"type":"string","format":"date-time","description":"Date and time the promo code exception list was deactivated (ISO 8601). Empty if the list is still active."},"NumberOfItems":{"type":"string","description":"The number of items in the promo code exception list."},"ItemsUri":{"type":"string","description":"API resource path for retrieving the items in this promo code exception list."},"Uri":{"type":"string","description":"Unique reference to the promo code exception list object in the impact.com API."}}}}}}
```

## The PromoCodeExceptionListItem object

```json
{"openapi":"3.1.0","info":{"title":"Partner Promo Code Exception Lists API","version":"16"},"components":{"schemas":{"PromoCodeExceptionListItem":{"type":"object","description":"An item within a promo code exception list that defines a specific promo code value triggering an alternate commission rate.","properties":{"Id":{"type":"string","description":"Unique identifier for the promo code exception list item."},"ListId":{"type":"string","description":"Unique identifier for the parent promo code exception list."},"Name":{"type":"string","description":"Display name of the promo code exception list item."},"Value":{"type":"string","description":"The promo code value this item matches against."},"MatchMode":{"type":"string","enum":["EQ","REGEX"],"description":"The matching methodology used to evaluate the promo code value. EQ matches exactly; REGEX matches using a regular expression."},"CreatedDate":{"type":"string","format":"date-time","description":"Date and time this item was added to the promo code exception list (ISO 8601)."},"Uri":{"type":"string","description":"Unique reference to the promo code exception list item in the impact.com API."}}}}}}
```


---

# 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://integrations.impact.com/partner-api-reference/reference/promo-codes-exception-lists/models.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.