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

# Rate limits

How Pylon limits API request volume and how to handle 429 responses

Pylon limits how many requests your organization can make to each API endpoint per minute.

## How limits apply

* **Per organization.** All API tokens in your organization share the same allowance. Creating more tokens does not raise it.
* **Per endpoint.** Each endpoint has its own allowance. For example, requests to `GET /issues` do not count against `POST /issues/search`.
* **Per minute.** Every endpoint uses one of three limits: 30, 120, or 300 requests per minute.

Each endpoint's limit is listed in its entry in the [API reference](/pylon-docs/developer/api/api-reference.md).

If your integration needs a higher limit on a specific endpoint, contact Pylon support.

## Response headers

| Header                   | When                         | Value                                                                                                                                     |
| ------------------------ | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| `X-Rate-Limit-Remaining` | Every response               | How many more requests you can make to this endpoint right now.                                                                           |
| `Retry-After`            | `429 Too Many Requests` only | Seconds to wait before the next request can succeed, rounded up to a whole second.                                                        |
| `X-Retry-After`          | `429 Too Many Requests` only | Seconds until your full per-minute allowance is restored. Capacity comes back gradually before then, so some requests can succeed sooner. |

A request over the limit returns `429` with the `rate_limited` error code. See [Errors](/pylon-docs/developer/api/errors.md).

## Handling 429 responses

* Watch `X-Rate-Limit-Remaining` and slow down as it nears zero, rather than waiting for a `429`.
* When you get a `429`, wait at least the number of seconds in `Retry-After` before retrying. Add backoff and jitter if you keep receiving `429` responses. `X-Retry-After` describes the longer wait until the full allowance is restored.
* Spread bulk jobs over time instead of sending them in bursts. Remember that every integration using your organization's tokens draws from the same allowance.
* Prefer search endpoints with filters and pagination over fetching objects one at a time.


---

# 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.usepylon.com/pylon-docs/developer/api/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.