# Rate Limits

To ensure fair usage and protect the stability of the platform, all requests to the Quinyx API v3 are subject to rate limiting. Rate limits define how many requests you can make within a given time window. This page covers how limits are applied and how your integration should handle being limited.

## How it works

- Limits are applied **per customer and per endpoint group**. Each API area has its own allowance, so exhausting the limit for one endpoint group does not affect your requests to the others.
- Every request counts toward your limit, regardless of the response status.
- When you exceed the allowed limit, the API responds with `429 Too Many Requests` and the request is not processed.


The exact limits, and the response headers that report your current usage, are not published yet. They will be documented on this page once they are finalized.

## Handling 429 responses

A `429 Too Many Requests` can also result from platform-level protection rather than from a limit specific to your integration. Handle it from the first day your integration runs rather than waiting for the limits above to be finalized.

- Retry with an exponential backoff. Do not retry immediately in a tight loop.
- Spread bulk operations over time instead of sending them in short bursts.
- Treat `429` as an expected response, not an exceptional one.