> For the complete documentation index, see [llms.txt](https://dev.apirtc.com/apirtc-developer-portal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.apirtc.com/apirtc-developer-portal/rest-apis-and-integration/rate-limits.md).

# Rate Limits

## Overview

To ensure optimal performance and fair usage of our API, we enforce rate limits on all API requests. These limits are in place to prevent abuse and to ensure that all users have equitable access to our services.

## Rate Limit Policy

Our API allows up to **10 requests per minute** per user. Exceeding this limit will result in rate limiting, preventing further requests until the time window resets.

#### Limit Details

* **Rate Limit:** 10 requests per minute
* **Scope:** Per user, across all endpoints

## Response Headers

When making API requests, you can monitor your current rate limit status via the following response headers:

* X-RateLimit-Reset: Time in seconds until the rate limit resets

#### Example Response Headers

```
X-RateLimit-Reset: 45
```

## Handling Rate Limits

If the rate limit is exceeded, the API will return an HTTP 429 Too Many Requests status code.

#### Example 429 Response

```
HTTP/1.1 429 Too Many Requests
Content-Type: application/json

{
  "error": "You have reached the maximum number of attempts. Please retry later."
}
```

## Best Practices

To avoid hitting rate limits:

* Implement exponential backoff in your retry logic.
* Optimize API calls to reduce redundancy.
* Cache responses where applicable to minimize repeated requests.
* Monitor the X-RateLimit-Remaining header to adjust request frequency dynamically.