Vapi · Rate Limits

Vapi Rate Limits

Vapi documents concurrency limits per account and applies standard 429 throttling on the REST API. Concurrent call limits scale with plan/contract; specific RPS quotas are not publicly documented and should be confirmed with Vapi support.

2 Limits Throttle: 429
AIVoiceAgentsRealtimeCPaaSRate LimitingQuotasThrottling

Limits

Concurrent Calls account
concurrent_calls
scales by plan; contact support for higher concurrency
Vapi enforces a per-account concurrent active call cap.
API Requests account
requests
not publicly documented
Standard 429 backoff applies; verify limits with Vapi support before high-volume integrations.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After header on 429 responses.
Concurrency Planning
Provision concurrent call capacity in advance for outbound campaigns and high-volume inbound use cases.

Sources