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

# Rate Limits

Understand ComplyCube API rate limits, retry strategy, exponential backoff, and webhook-based alternatives.

ComplyCube’s API enforces the following maximum request rates:

* **Live environment**: up to **10 requests per second**.
* **Test (Sandbox) environment**: up to **5 requests per second**.

Requests that exceed these limits may be throttled or temporarily blocked.

Any request that exceeds the allowed rate will receive a `429 Too Many Requests` response.

{% hint style="info" %}
You should implement suitable error handling for `429` errors. Using an **exponential backoff** strategy with random jitter is the recommended approach to safely retry requests and avoid repeated throttling.
{% endhint %}

### Avoiding the limit

To help prevent reaching rate limits, consider the following best practices:

* Run non-essential or routine batch jobs outside of peak hours.
* Throttle or limit the frequency of batch jobs.
* Implement exponential backoff for retries, starting with a 30-second delay.
* Prioritize requests that are essential to verifying active clients.
* Use webhooks instead of polling our API for updates.


---

# 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://docs.complycube.com/documentation/api-reference/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.