100ms · Rate Limits

100Ms Live Rate Limits

Rate-limit and quota model for the 100ms Server-Side API and the underlying live media plane. 100ms does not publish per-endpoint REST rate-limit headers on the Server-Side API; control-plane abuse is bounded by overall request volume and account-level fair use. The hard caps that practically govern the platform are the in-session concurrency caps (peers per room, sessions per app, recordings per account) and the per-region capacity caps negotiated on Enterprise plans.

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

It captures 5 rate-limit definitions.

The profile also includes response codes documented for throttled and quotaExceeded.

Tagged areas include Live Video, Rate Limiting, and Quotas.

5 Limits Throttle: 429 Quota: 429
Live VideoRate LimitingQuotas

Limits

room
Default upper bound for a standard room. Higher caps require enabling large_room=true on the room or moving to Enterprise.
room
`large_room: true` rooms use a different SFU topology and unlock 10k+ concurrent peers (the same primitive that powers IPL on JioCinema/Hotstar). Higher than 10k requires Enterprise contract and capacity reservation.
live-stream
HLS playback scales horizontally through the CDN; viewer count is bounded by output minutes (billed) rather than a hard cap.
account
Management JWT must include an `exp` claim no further than 24 hours in the future.
account
100ms retries failed webhook deliveries with exponential backoff over ~24h; replay is available via /v2/analytics/events/replay.

Sources