> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/developer/api/cep/catalogs.md).

# Catalogs

Catalogs API allow brands to **Create**, **Update**, **Remove**, **List**, **View** and **Edit** catalog items, making it easy to maintain up-to-date content—like products, events, or offers—that can be dynamically injected into your campaigns or automations.

#### Rate Limiting

See [global CEP API rate limiting](/developer/api/cep.md#rate-limiting).

To ensure fair usage and platform stability, all Catalog API endpoints are subject to rate limiting.

**General Catalog API rate limit**

All Catalog API endpoints (including **Create**, **Update**, **Remove**, **View**, **Replace** and **List**) are limited to **5 requests per second**. If the limit is exceeded, the API returns an HTTP `429 Too Many Requests` response. When this occurs, please wait a few seconds before retrying.

**Specific limit for /catalogs/items/edit**

The **/catalogs/items/edit** endpoint has additional operational limits due to its higher data throughput:

* Up to **5 requests per second**.
* Up to **1,000 items updated per second**.
* Each item in your payload counts as one update toward the limit.

If either threshold is exceeded, the API will respond with an HTTP `429 Too Many Requests` error.\
When that happens, slow down your requests or reduce the batch size to comply with the limit.

{% content-ref url="/pages/E2aQ3bT3Y1bahCjFLmf3" %}
[Create catalog](/developer/api/cep/catalogs/create.md)
{% endcontent-ref %}

{% content-ref url="/pages/MWyo9GQX6VgtjBoqso0w" %}
[Remove catalog](/developer/api/cep/catalogs/remove.md)
{% endcontent-ref %}

{% content-ref url="/pages/AlcA5MfmK52MqRzEasvx" %}
[List catalogs](/developer/api/cep/catalogs/list.md)
{% endcontent-ref %}

{% content-ref url="/pages/9lYx5IDinQtFGa2Cxy69" %}
[Update catalog](/developer/api/cep/catalogs/update.md)
{% endcontent-ref %}

{% content-ref url="/pages/ygaj868CduqggG3QBr3d" %}
[View catalog](/developer/api/cep/catalogs/view.md)
{% endcontent-ref %}

{% content-ref url="/pages/hsU67YHgKAWvPuIZVnIv" %}
[Edit catalog items](/developer/api/cep/catalogs/edit-items.md)
{% endcontent-ref %}

{% content-ref url="/pages/7qx74Nd9HpLF45rQwrdj" %}
[Replace start](/developer/api/cep/catalogs/replace-start.md)
{% endcontent-ref %}

{% content-ref url="/pages/sFP1tuJK2LrvITx83l1T" %}
[Replace items](/developer/api/cep/catalogs/replace-items.md)
{% endcontent-ref %}

{% content-ref url="/pages/ZTWUZYWyyvY2daAjCbov" %}
[Replace complete](/developer/api/cep/catalogs/replace-complete.md)
{% endcontent-ref %}

{% content-ref url="/pages/Lsdmg08o74GWTBbnb95y" %}
[Replace cancel](/developer/api/cep/catalogs/replace-cancel.md)
{% endcontent-ref %}


---

# 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://doc.batch.com/developer/api/cep/catalogs.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.