> 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/brand-api-reference/reference/exception-lists.md).

# Exception Lists

*Exception Lists* are used to pay partners different rates based on the category or the SKU associated with the action they drove. You can use this endpoint to manage your exception lists and create new ones, as well as manage, create, and remove items on each exception list you have.

While all brands have access to `Category` exception lists, only *Pro* and *Enterprise* brands have access to `SKU` exception lists. If you interested in `SKU` exception lists, reach out to your CSM (or [contact support](https://app.impact.com/support/portal.ihtml?createTicket=true)).

See the [Category Lists screen](https://app.impact.com/secure/advertiser/campaign/itemlist/view-categoryitemlist-flow.ihtml) to manage category lists via the impact.com web app.


---

# 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://integrations.impact.com/brand-api-reference/reference/exception-lists.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.