> For the complete documentation index, see [llms.txt](https://docs.exads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exads.com/api/exads-public-api/api-manual-rate-limiting.md).

# Rate Limiting

## Request limits

The API is rate-limited. Limits apply per username and per IP address, and statistics requests have their own, lower limit. Limits are set for each network and can change, so don't build your integration around fixed numbers.

Every response includes the current rate limit details in its HTTP headers:

* `X-Rate-Limit-Limit`: the number of requests allowed in the current window
* `X-Rate-Limit-Remaining`: the number of requests you have left
* `X-Rate-Limit-Reset`: the number of seconds until the limit resets

When you exceed the limit, requests return `429 Too Many Requests` until the limit resets. Use the headers to slow down before you reach the limit.

## Examples <a href="#examples" id="examples"></a>

The values below are examples only.

### Rate Limiting - Example 1 <a href="#rate-limiting---example-1" id="rate-limiting---example-1"></a>

```bash
$ curl -i https://api.example.com/v2/statistics/a/date
```

```http
    {
        "HTTP/1.1": "200 OK",
        "Date": "Fri, 24 Oct 2014 14:57:32 GMT",
        "Content-Type": "application/json",
        "Transfer-Encoding": "chunked",
        "X-Rate-Limit-Limit": 100,
        "X-Rate-Limit-Remaining": 99,
        "X-Rate-Limit-Reset": 27
    }
```

### Rate Limiting - Example 2 (Limit Exceeded) <a href="#rate-limiting---example-2-limit-exceeded" id="rate-limiting---example-2-limit-exceeded"></a>

```bash
$ curl -i https://api.example.com/v2/statistics/a/date
```

```http
{
        "HTTP/1.1": "429 Too Many Requests",
        "Date": "Fri, 24 Oct 2014 15:04:35 GMT",
        "Content-Type": "application/json",
        "Transfer-Encoding": "chunked",
        "X-Rate-Limit-Limit": 100,
        "X-Rate-Limit-Remaining": 0,
        "X-Rate-Limit-Reset": 12
    }
```


---

# 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://docs.exads.com/api/exads-public-api/api-manual-rate-limiting.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.
