Exotel · Rate Limits

Exotel Rate Limits

Exotel documents a per-minute throughput cap on its Voice APIs and returns HTTP 429 when exceeded. Its developer docs state Voice APIs are limited to around 200 calls per minute. SMS and other product limits are governed by account plan, sender/DLT approvals, and telecom regulations rather than a single published per-endpoint number. Values here are grounded where the docs state a figure and flagged otherwise.

Exotel Rate Limits is the machine-readable rate-limit profile for Exotel on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests, messages, characters, minutes, and usage.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Cloud Telephony, Voice, SMS, CPaaS, and Rate Limiting.

5 Limits Throttle: 429
Cloud TelephonyVoiceSMSCPaaSRate LimitingQuotas

Limits

Voice API Calls account
requests
~200 per minute
Documented cap on Voice APIs; exceeding it returns HTTP 429.
Bulk SMS Batch Size request
messages
up to 100 messages per request
Bulk SMS (static/dynamic) accepts up to 100 messages per call per docs.
SMS Body Length request
characters
up to 2000 characters
Documented maximum SMS Body length.
AgentStream Session Duration stream
minutes
up to 60 minutes per streaming session
Documented max WebSocket voice-streaming session length; plan-dependent.
Account / Plan Quotas account
usage
per plan
Not published numerically; governed by plan and DLT/sender approvals.

Policies

Throttling Response
Requests over the documented Voice API rate return HTTP 429; back off and retry.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses.
Streaming Timeout
If a bot server does not respond within ~10 seconds during an AgentStream session, the session fails.

Sources