---
title: Rate Limits
slug: voice-apis/rate-limits
docTags: 
createdAt: 2026-01-20T03:33:07.652Z
---

## Introduction

To ensure platform stability and fair usage across all customers, Exotel enforces **rate limits** on API requests.

Rate limits apply **per account** and are evaluated based on **API type and request volume**. 

## Default Limit

Default limit for all API is **100 RPM** which can be increased based on request to us. If you exceed the rate limit, you will receive a 429 HTTP response code. Please ensure that your application adheres to the rate limits to avoid disruptions in service.

## How Rate Limiting Works

- Rate limits are applied at the **account level** 
- Limits may vary based on: 
  - API category (Legs, Bridges, Actions, Events) 
  - Region 
  - Contractual plan 
- Both **burst limits** and **sustained request limits** may apply 

## Rate Limit Exceeded Response

If a request exceeds the allowed rate limit, the API responds with:

### HTTP Status Code

:::BlockQuote
429 Too Many Requests
:::

### Sample Response

:::BlockQuote
\{
  "request\_id": "xyz123",
  "http\_code": 429,
  "response": \{
    "error": \{
      "code": "RATE\_LIMIT\_EXCEEDED",
      "message": "Rate limit exceeded. Please retry after some time."
    }
  }
}
:::

## Best Practices

- Implement **retry logic with exponential backoff** 
- Avoid sending multiple concurrent actions on the same leg or bridge 
- Batch workflows where possible instead of polling 
- Use **external events (gRPC)** instead of frequent status checks 

## Increasing Rate Limits

If your use case requires higher throughput (for example, large-scale outbound calling or real-time orchestration):

- Contact your **Exotel account manager** 
- Share: 
  - Expected request volume 
  - API categories used 
  - Peak traffic patterns 

Custom rate limits may be provisioned based on use case and plan.

## Notes

- Rate limits are enforced to protect platform reliability 
- Repeated violations may result in **temporary throttling** 
- Rate limits apply uniformly across **production and sandbox environments**, unless explicitly stated otherwise