> For the complete documentation index, see [llms.txt](https://docs.shadowcipher.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shadowcipher.in/reference/rate-limits.md).

# Rate limits

Request limits per IP address and per client.

Limits apply **per IP address** and **per client**.

| Endpoint                | Limit                  |
| ----------------------- | ---------------------- |
| `POST /api/oauth/token` | 5 requests per minute  |
| All other endpoints     | 60 requests per minute |

## Headers

Every response tells you where you stand:

| Header                         | Description                                      |
| ------------------------------ | ------------------------------------------------ |
| `X-RateLimit-Limit-IP`         | Requests allowed per window for your IP address. |
| `X-RateLimit-Remaining-IP`     | Requests left in the current window for your IP. |
| `X-RateLimit-Reset-IP`         | When the IP window resets.                       |
| `X-RateLimit-Limit-Client`     | Requests allowed per window for your client.     |
| `X-RateLimit-Remaining-Client` | Requests left for your client.                   |
| `X-RateLimit-Reset-Client`     | When the client window resets.                   |

## When you go over

You get `429 Too Many Requests` with a `Retry-After` header (seconds):

```json
{
  "error": "rate_limit_exceeded",
  "error_description": "Too many requests from this client. Try again in 42 seconds.",
  "retry_after": 42
}
```

Wait for `Retry-After` seconds before trying again.

{% hint style="info" %}
Tokens last 30 minutes. Reuse one token for all calls in that window instead of requesting a new token per call, which keeps you well under the token limit.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.shadowcipher.in/reference/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.
