For clean Markdown of any page, append .md to the page URL. For a complete documentation index, see https://documentation.apexverify.com/api-reference/llms.txt. For full documentation content, see https://documentation.apexverify.com/api-reference/llms-full.txt.

# API Rate Limits

To ensure platform stability, fair usage, and optimal performance across all tenants, the ApexVerify API enforces rate limits on your requests. Our infrastructure implements a **token bucket algorithm** for precise allocation.

## Maximum Throughput

All API consumers are bounded by a standard limit of **180 requests per minute**.

## Rate Limit Headers

Every successful or failed API response includes HTTP headers to help your application programmatically track its current rate limit status and consumption.

| HTTP Header             | Description                                                                        |
| :---------------------- | :--------------------------------------------------------------------------------- |
| `X-RateLimit-Limit`     | The total number of requests permitted within the allocated time window.           |
| `X-RateLimit-Remaining` | The number of requests remaining in the current window before limits are enforced. |
| `X-RateLimit-Used`      | The number of requests already consumed in the current window.                     |

## Handling Rate Exceeded Errors

If your integration attempts to make requests exceeding the limit, the API will refuse the connection and respond with a `429 Too Many Requests` HTTP status code.

To facilitate exponential backoff strategies, the response will also include a `Retry-After` header. This header specifies the number of seconds your application must pause before resuming requests.

```http
HTTP/1.1 429 Too Many Requests
Retry-After: 44
X-RateLimit-Limit: 180
X-RateLimit-Used: 180
X-RateLimit-Remaining: 0
Content-Type: application/json

{
  "message": "Too Many Requests"
}
```