> 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/brand-api-reference-v11/readme/rate-limits.md).

# Rate Limits

The impact.com application programming interface (API) limits how many calls a client can make in a given hour to help protect our system against traffic spikes that could disable it.

## Response headers

If the number of requests you are trying to make exceeds your limit, your requests will be throttled and we will respond with a `429 - Too Many Requests` response along with the following headers:

| Header                           | Description                                                                                                                                           |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| `X-RateLimit-Limit-<window>`     | Maximum requests allowed in the window. `<window>` is `hour` for hourly limits, `day` for daily limits, and `600` for the 10-minute job replay limit. |
| `X-RateLimit-Remaining-<window>` | Requests remaining in the current window.                                                                                                             |
| `RateLimit-Limit`                | Maximum requests allowed in the current window.                                                                                                       |
| `RateLimit-Remaining`            | Requests remaining in the current window.                                                                                                             |
| `RateLimit-Reset`                | Seconds until the current window resets.                                                                                                              |
| `Retry-After`                    | Only on `429` responses. Seconds to wait before retrying.                                                                                             |

## Hourly rate limits

Endpoints are grouped, and all endpoints in a group share that group's limit.

| Group         | Limit                    | Endpoints                                                                                                     |
| ------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------- |
| Batch logging | 40,000 requests per hour | FTP submissions, API submissions, batch summaries and details, and the file batch generator                   |
| Catalogs      | 3,600 requests per hour  | `/Catalogs`, `/FinancialCatalogs`, and program `BrandStores`, `MediaUploads`, `Products`, and `ProductGroups` |
| Reports       | 1,000 requests per hour  | `/Reports`                                                                                                    |
| Jobs          | 1,000 requests per hour  | `/Jobs`                                                                                                       |
| General       | 1,000 requests per hour  | All other endpoints, including `GET /Actions` and `/ActionUpdates`                                            |

## Other limits

These endpoints have their own limits, separate from the hourly limits.

| Group         | Limit                       | Endpoints                           |
| ------------- | --------------------------- | ----------------------------------- |
| Job replay    | 100 requests per 10 minutes | `/Jobs/{Id}/Replay`                 |
| Report export | 100 requests per day        | `/ReportExport`                     |
| Click export  | 10 requests per day         | `/Programs/{ProgramId}/ClickExport` |

Job replay, report export, and click export requests count only toward their own limit. They don't count toward the general hourly limit.

## Endpoints without rate limits

The following endpoints aren't rate limited:

* `POST`, `PUT`, and `DELETE` on `/Actions`
* `/MobileEvents`, `/MobileDetails`, `/Conversions`, and `/AppEvents`
* `/Campaigns/{Id}/Media/{Id}/EmailEvents` and `/Campaigns/{Id}/Media/{Id}/Iterable`

Rate limits are subject to change at any given time based on the needs of the system. It's best practice for applications to monitor their current rate limit status and dynamically throttle requests if necessary.

## Example rate limit responses

These examples show the headers in a successful response and in a rate-limited response.

***

### Request within the limit

{% code collapsedlinecount="10" %}

```http
HTTP/1.1 200 OK
X-RateLimit-Limit-hour: 1000
X-RateLimit-Remaining-hour: 999
RateLimit-Limit: 1000
RateLimit-Remaining: 999
RateLimit-Reset: 2400
```

{% endcode %}

### Limit exceeded

{% code collapsedlinecount="10" %}

```http
HTTP/1.1 429 Too Many Requests
X-RateLimit-Limit-hour: 1000
X-RateLimit-Remaining-hour: 0
RateLimit-Limit: 1000
RateLimit-Remaining: 0
RateLimit-Reset: 700
Retry-After: 700

{"message":"API rate limit exceeded"}
```

{% endcode %}


---

# 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://integrations.impact.com/brand-api-reference/brand-api-reference-v11/readme/rate-limits.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.
