# Rate Limiting Policy

## How Rate Limiting Works

Each tenant is limited to **600 API requests per minute** on all **public-facing APIs**. This limit maintains fair usage and system stability. Rate limits apply **globally across all public APIs per tenant**. If the limit is exceeded, the API responds with **HTTP 429 – Too Many Requests**.

***

### Event Log Example

Rate limit details are recorded in the event log:

```json
{
  "x-ratelimit": 600,
  "x-ratelimit-remaining": 450,
  "x-ratelimit-reset": 1632425760
}
```

***

### Exceeding the Limit

If the request limit is exceeded, the API responds:

```
HTTP/1.1 429 Too Many Requests
```

The event log shows the limit, remaining requests, and reset time.

***

### Best Practices

* **Retry Logic** – If you receive an HTTP 429 response, use the reset time from the event log to determine when it is safe to retry requests.
* **Monitor Usage** – Regularly review the event log to track request volumes and avoid recurring limit breaches.

***

## Request Higher API Rate Limits

If your workloads require higher public API request capacity, please contact <support@simptel.com>\
to discuss an increase in rate limits.

**How to request:**

1. Have your **Tenant ID** ready.
2. Email **<support@simptel.com>** with subject **“API Rate Limit Increase”**.
3. Include your **Tenant ID** and desired requests per minute, expected peak/average volume, and timeline.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.simptel.com/tf-platform/administration/support/rate-limiting-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.