Dyte · Rate Limits

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.

4 Limits Throttle: 429
VideoVoiceReal TimeWebRTCCommunicationsRate LimitingQuotasThrottling

Limits

REST API Requests organization
requests
see provider documentation
Management API calls (meetings, participants, recordings, livestreams, sessions, webhooks) are rate limited per organization; numeric values not published.
Concurrent Participants per Meeting meeting
participants
see provider documentation
Concurrency caps vary by plan and meeting type (group call vs. webinar/livestream).
Concurrent Meetings organization
meetings
see provider documentation
Number of simultaneously active meetings varies by plan.
Webhook Subscriptions organization
webhooks
see provider documentation
Number of registered webhook endpoints per organization.

Policies

Tiered Limits
Limits and concurrency raise from free to paid and Enterprise / Cloudflare RealtimeKit agreements.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources