Dyte Rate Limits
Dyte's v2 REST API is authenticated with HTTP Basic auth (organizationId:apiKey) and enforces per-organization rate limits on management calls (creating meetings, adding participants, starting recordings/livestreams, querying sessions). Concurrent usage is governed primarily by the participant-minute model and per-meeting concurrency rather than per-second request quotas. Specific numeric per-endpoint limits are not published in detail and are not reconciled in this artifact, and may change as the platform migrates to Cloudflare RealtimeKit.
Dyte Rate Limits is the machine-readable rate-limit profile for Dyte on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests, participants, meetings, and webhooks.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Video, Voice, Real Time, WebRTC, and Communications.
Limits
Policies
Sources
- https://docs.dyte.io/
- https://docs.dyte.io/guides/rest-apis/quickstart
- https://www.cloudflare.com/developer-platform/products/cloudflare-realtime/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.