> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.noyax.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rate limits

> Daily request allowance per API key and the limit headers.

Every API key has a **daily request limit** set by Noyax. The counter is kept per API key: all of your servers using the same key share the same limit.

## Headers

Every response that passes the permission check includes your remaining allowance:

| Header              | Meaning                        |
| ------------------- | ------------------------------ |
| `X-Daily-Limit`     | Daily request limit of the key |
| `X-Daily-Remaining` | Requests left today            |

```http theme={null}
HTTP/1.1 200 OK
X-Daily-Limit: 10000
X-Daily-Remaining: 9874
```

## When the limit is reached

Once the limit is used up, requests are not processed and the API returns **429**:

```json theme={null}
{
  "Success": false,
  "ResultCode": "0120",
  "Message": "Daily request limit (10000) exceeded.",
  "Errors": [
    { "Code": "0120", "Message": "Daily request limit (10000) exceeded." }
  ]
}
```

The counter resets every day at **midnight Turkey time (UTC+3)**. Retrying on the same day after a 429 will not succeed.

## What counts?

* **All requests** that pass token, header and permission checks count, including those that end with a business rule error (400, 404).
* Requests rejected with an invalid token (401), a header error (400) or a permission error (403) **do not count**.

## Tips

* Use a large `pageSize` (up to 50) on list endpoints to reduce the number of requests.
* Cache data that rarely changes on your side.
* Watch `X-Daily-Remaining` and postpone bulk jobs when it runs low.
* If you need a higher limit, contact Noyax support. The new limit takes effect when you get a new token.