> For the complete documentation index, see [llms.txt](https://developers.gurupay.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.gurupay.eu/getting-started/api-concepts/rate-limits.md).

# Rate Limits

To ensure fair use and protect system stability, Guru Pay enforces rate limiting on all Public API requests.

## Rate Limit Headers

Each API response includes headers to help you monitor your usage in real time:

| Header                  | Description                                             |
| ----------------------- | ------------------------------------------------------- |
| `X-RateLimit-Limit`     | The maximum number of requests allowed per minute.      |
| `X-RateLimit-Remaining` | THe number of remaining requests in the current window. |

## Current Limit

* Limit: `500` requests per minute
* Applies to: Each IP address

This means your application can make up to **500 API requests per minute** from a single IP address. Requests exceeding this limit will be temporarily blocked.

## What Happens If You Go Over?

If your application exceeds the limit:

* You will receive an HTTP **429 Too Many Requests** response.
* You must wait **at least 1 minute** before retrying.

**Example 429 Error Response:**

```json
{
    "status": false,
    "status_code": 429,
    "message": "Too Many Attempts.",
    "errors": [
        "Too Many Attempts."
    ]
}
```


---

# 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://developers.gurupay.eu/getting-started/api-concepts/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.
