Dolby Io Rate Limits
Dolby.io / OptiView does not publish per-account REST rate-limit numbers for the Real-time Streaming or Live APIs. The platform enforces account-level resource limits (concurrent streams, concurrent viewers, transcoder count, bandwidth) negotiated as part of the customer contract. Public documentation calls out four practical constraints: - Webhook delivery is fire-and-forget (no retries on failure). - Webhook payload order is not guaranteed. - Bound-IP subscribe tokens enforce a hard cap on simultaneous IPs after first use. - REST tokens (publish, subscribe) carry per-token activity flags and expiration.
Dolby Io Rate Limits is the machine-readable rate-limit profile for Dolby.io on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions.
The profile also includes response codes documented for throttled and quotaExceeded.
Tagged areas include Streaming, WebRTC, and Rate Limiting.
Limits
Sources
- https://optiview.dolby.com/docs/millicast/webhooks/
- https://optiview.dolby.com/docs/millicast/managing-your-tokens/
- https://optiview.dolby.com/docs/millicast/getting-started/using-rest-apis/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.