CometChat · Rate Limits

Cometchat Rate Limits

CometChat enforces account-level limits scoped to a single app and region. The primary commercial limits are Monthly Active Users (MAU) and concurrent WebSocket connections, both set by the subscription tier; exceeding them triggers overage billing rather than hard rejection on paid plans. The REST Management API additionally applies per-app request throttling. Specific per-endpoint request-per-second values are not publicly enumerated and are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring mau, connections, requests, and items.

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

Tagged areas include Chat, Messaging, Voice, Video, and SDK.

4 Limits Throttle: 429
ChatMessagingVoiceVideoSDKRealtimeRate LimitingQuotasThrottling

Limits

Monthly Active Users (MAU) account
mau
per plan
Distinct users active per month; overage billed at $0.10/MAU on paid tiers.
Concurrent Connections account
connections
per plan
Included as a percentage of MAU (5% Basic/Advanced, 10% Enterprise); $1 per extra connection except Enterprise.
REST API Requests app
requests
see provider documentation
Per-app request throttling on the v3 Management API; specific RPS not publicly documented.
Pagination Page Size request
items
100
perPage query parameter caps list responses (default 25).

Policies

Tiered Limits
MAU and concurrent-connection allotments scale with the subscription tier; Enterprise removes overage charges.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 and honor Retry-After when present.

Sources