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

# Exception Lists

Brands use *Exception Lists* to pay different rates based on the category or the SKU associated with the action you drove. You can use this endpoint to retrieve exception lists and exception list items.

### Query the exception list endpoint

The following steps explain how you’ll get access to the exception list ID to query the endpoint:

1. Query the [Contracts API](broken://pages/8141b6449bece1ab0754a25ada265489aab09eae#get-mediapartners-accountsid-campaigns-campaignid-contracts-active) to get the list of exception list IDs, if any, on a given contract.
2. After getting the exception list ID(s), query the exception lists 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 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/partner-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.