Rate Limits

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 429 too many requests sample response { "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