> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/partner/what-would-you-like-to-learn-about/platform-features/working-with-brands/contracts/get-a-sku-list-for-boosted-payouts.md).

# Get a SKU List for Boosted Payouts

If your partnered brand created a Product Boost campaign with [boosted payouts](/partner/what-would-you-like-to-learn-about/platform-features/working-with-brands/contracts/boosted-product-payouts-explained.md) for specific product SKUs, you can follow the steps below to list those items and identify which products to prioritize in your promotions.

#### Step 1: Retrieve the contract’s campaign terms

Use the [contracts API](https://integrations.impact.com/impact-publisher/reference/contracts-overview) to retrieve your contract with the brand that created the Product Boost campaign.

* Follow the example request in the [Retrieve a contract](https://integrations.impact.com/impact-publisher/reference/retrieve-contract) reference.

  * Make sure to include the correct credentials and relevant contract `Id`.

  <div data-with-frame="true"><figure><img src="/files/YyOKmI23uyLFbtMPpSY4" alt="" width="556"><figcaption></figcaption></figure></div>

#### Step 2: Look for SKU exception lists

Check for SKU exception lists in your API response.

1. In your API response, navigate to the `CampaignTerms` attribute to see its `PayoutGroups`.
2. Identify any payout group `Rules` with the `Variable` value `“ITEM_SKU_LIST”`.
3. Take note of the SKU list’s identifier, as you’ll use it in the next step.

   * E.g., if `ITEM_SKU_LIST` `IS` `11356`  → “**11356**” is the identifier.

   <div data-with-frame="true"><figure><img src="/files/TmhRQUQXIYecjJtRKF1U" alt="" width="489"><figcaption></figcaption></figure></div>

#### Step 3: List items in the exception list

Use the [exception list API](https://integrations.impact.com/impact-publisher/reference/exception-lists-overview) to list specific products with boosted payouts.

1. Follow the example request in the [List all items for an exception list](https://integrations.impact.com/impact-publisher/reference/list-all-items-for-an-exception-list) reference.
   * Make sure to enter the correct credentials and the relevant `ExceptionListId` (use the SKU list’s identifier from earlier).
2. Your API response will return each item on the SKU exception list with the following details:

   <div data-with-frame="true"><figure><img src="/files/AhLpgACYXTyo3roE1oFU" alt="" width="539"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Tip:** Consider asking your technical team to automate this process, e.g., set up logic to automatically identify when a Product Boost campaign term includes `ITEM_SKU_LIST`.
{% endhint %}


---

# 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://help.impact.com/partner/what-would-you-like-to-learn-about/platform-features/working-with-brands/contracts/get-a-sku-list-for-boosted-payouts.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.