> For the complete documentation index, see [llms.txt](https://docs.violet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violet.io/api-reference/catalog/offers/get-all-merchant-offers-lightweight.md).

# Get All Merchant Offers (Lightweight)

Retrieve a lightweight list of all `Offer`'s for a Merchant, given their `merchant_id`. Unlike the [standard endpoint](/api-reference/catalog/offers/get-all-merchant-offers.md), this version does **not** eagerly load SKUs, variants, or albums, significantly reducing payload size and response time.

Use this endpoint when you only need offer-level fields such as name, price, merchant, and status — for example, in dashboard views or listing pages.

{% hint style="info" %}
This endpoint supports the same filtering, pagination, and currency parameters as the [standard Get All Merchant Offers](/api-reference/catalog/offers/get-all-merchant-offers.md) endpoint. Maximum page size is `100`.
{% endhint %}

{% hint style="info" %}
To avoid performance issues, `total_elements` and `total_pages` properties are not populated for this endpoint response, being both returned with default value of `0`.
{% endhint %}

{% hint style="info" %}
Violet **strongly** discourages scraping this endpoint. Most offers do not change very often,\
so re-scraping all of a merchant's offers on a regular basis is a very costly way to keep your catalog up to date.

Violet's recommendation is to make use of [offer webhooks](https://app.gitbook.com/s/ZrOgj5n6PuU2r0Ya8Tzl/prism/checkout-guides/webhooks/handling-webhooks) to be notified when offers are added/updated in Violet's system.\
This works because when your merchants onboard, their products are pulled into Violet's system and so you will receive a webhook for each of the new merchant's offers.\
Additionally, Violet employs a number of methods to keep our merchant's catalogs up to date and all of those methods will generate webhooks sent to your system.
{% endhint %}

{% openapi src="/files/bEbkEBPLf0IRBDBqq1jM" path="/catalog/offers/merchants/{merchant\_id}/v1.1" method="get" expanded="true" %}
[catalog-service.yaml](https://3937396275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8lXIp71Ct5qCUhXjko2q%2Fuploads%2Fgit-blob-31bd87e3d3ec1260cad05c3ee2fd530338feb651%2Fcatalog-service.yaml?alt=media)
{% endopenapi %}


---

# 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://docs.violet.io/api-reference/catalog/offers/get-all-merchant-offers-lightweight.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.