Vonage Video API · Rate Limits

Vonage Video Rate Limits

The Vonage Video REST API enforces per-application rate limits on server-side operations (session creation, signaling, archiving, broadcast, SIP, render, and moderation calls), plus platform concurrency limits on simultaneous sessions, publishers per session, archives, and broadcasts. Signaling has per-connection rate and payload-size limits enforced on the client and server. Specific numeric limits vary by account tier and are not published as a single table; they are not reconciled in this artifact.

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

It captures 7 rate-limit definitions, measuring requests, signals, bytes, publishers, and sessions.

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

Tagged areas include Video, WebRTC, Live Streaming, Real-Time Communications, and CPaaS.

7 Limits Throttle: 429
VideoWebRTCLive StreamingReal-Time CommunicationsCPaaSRate LimitingQuotasThrottling

Limits

REST API Requests application
requests
see provider documentation
Server-side REST operations are rate limited per application; exceeding returns 429.
Signaling Rate connection
signals
see provider documentation
Per-connection signal rate limit; excess signals are dropped or rejected.
Signal Payload Size request
bytes
8192
Signal data payload is limited to roughly 8 KB per signal.
Publishers Per Session session
publishers
see provider documentation
Concurrent active publishers per routed session; affects participant-minute pricing tier.
Concurrent Sessions application
sessions
see provider documentation
Concurrent live sessions per application, varies by account tier.
Concurrent Archives application
archives
see provider documentation
Concurrent recording archives per application.
Concurrent Broadcasts application
broadcasts
see provider documentation
Concurrent live streaming broadcasts per application.

Policies

Tiered Limits
Concurrency and rate limits raise as accounts move from trial to paid and Enterprise agreements.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor Retry-After.
Callback Retry
Secure callback delivery is retried with backoff for up to 24 hours before the event is dropped.

Sources