SuperViz · Rate Limits

Superviz Rate Limits

SuperViz meters usage primarily through plan allowances - monthly active users / concurrent connections, realtime messages per month, and video / recording minutes - rather than fixed per-second REST rate limits. Server-side REST calls (presence, channels, publish event, rooms, comments, meetings) authenticated with client_id / secret are subject to standard abuse protection. Specific per-endpoint request-per-second limits are not published and are not reconciled in this artifact.

Superviz Rate Limits is the machine-readable rate-limit profile for SuperViz on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring connections, messages, minutes, and requests.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Real Time, Collaboration, Presence, Synchronization, and Rate Limiting.

4 Limits Throttle: 429
Real TimeCollaborationPresenceSynchronizationRate LimitingQuotasThrottling

Limits

Concurrent Connections account
connections
see plan allowance
Bounded by MAU / concurrent-connection allowance of the active plan.
Realtime Messages account
messages
see plan allowance
Monthly realtime message allowance per plan; overage billed on paid tiers.
Video Meeting Minutes account
minutes
see plan allowance
Participant-minutes of video huddle, metered per plan.
REST Requests account
requests
see provider documentation
Server-side REST endpoints share standard abuse-protection throttling; specific per-second caps are not published.

Policies

Plan Allowances
Limits are set by the account's plan (Free / Pro / Enterprise) and raised via upgrades or enterprise agreements.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor any Retry-After header.

Sources