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, in the API Commons Rate Limits shape.

It captures 4 rate-limit definitions, measuring requests, participants, meetings, and webhooks.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-06-20.
Written by API Evangelist on 2026-06-20 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/dyte-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.