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

# Rate Limiting

Our API enforces rate limiting to ensure fair usage and optimal performance. The rate limit is variable based on the API.

During account setup your API rate limits will be set based on expected volumes.

If you exceed this limit, you will receive a **429 Too Many Requests** response. To avoid being rate-limited:

* Implement request queuing or throttling in your application.
* Monitor your API usage to ensure it stays within the limit.

#### Rate-Limiting Response Headers

Each API response includes the following headers to help you monitor your usage:

* **x-ratelimit-limit**: The maximum number of requests allowed within the time window (e.g., **50**).
* **x-ratelimit-remaining**: The number of requests remaining in the current time window.

#### Example Response Headers

```json
x-ratelimit-limit: 150
x-ratelimit-remaining: 100
```


---

# 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://detected.gitbook.io/detected-docs/api-overview/rest-apis/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.