Dolby.io · Rate Limits

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.

4 Limits Throttle: 429 Quota: 429
StreamingWebRTCRate Limiting

Limits

account
Concurrent publish streams, concurrent viewers, recording hours, and bandwidth are negotiated per contract; no public RPM/RPS published.
webhook
Fire-and-forget delivery, no retries, no ordering guarantees. HMAC-SHA1 signed payloads.
account
Concurrent channels, transcoder minutes, viewer minutes, and bytes transferred negotiated per contract.
account
Media job concurrency tied to the legacy $25/month free credit and pay-as-you-go billing.

Sources