> For the complete documentation index, see [llms.txt](https://ninjapay.gitbook.io/ninjapay-api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ninjapay.gitbook.io/ninjapay-api-docs/how-to/api-reference-upi/limits-on-api-requests.md).

# Limits on API Requests

In order to provide fast response times to all our customers, we may limit excessive requests made to the Ninjapay API. The limits are specific to the type of operation and allow for a certain number of requests to be made within a given time period.

The following API request limits are in effect and subject to change:

| Operation                | Endpoint                      | Limit                       | Timeout  |
| ------------------------ | ----------------------------- | --------------------------- | -------- |
| Payment request          | /v1/receive                   | 150 requests / 1 minute     | 1 minute |
| Payment quote generation | /v1/invoices/:invoiceId/quote | 150 requests / 1 minute     | 1 minute |
| All others               | All others                    | 1,000 requests / 10 minutes | 1 hour   |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ninjapay.gitbook.io/ninjapay-api-docs/how-to/api-reference-upi/limits-on-api-requests.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.