Published rate-limit posture
| Surface | Current published status |
|---|
| Connection and subscription control | The current AsyncAPI artifact defines the message flow, not a numeric quota table |
| Feed delivery cadence | Server-driven; clients do not poll for updates |
| Numeric quotas or tiers | Not currently rendered on this Mintlify surface |
What this page can answer safely
| Question | Public answer |
|---|
| whether the public realtime family publishes a numeric quota table today | it does not |
| which control-plane failure channel is currently documented | ACKNOWLEDGE.result.error plus the documented realtime error surfaces |
| what exact live hosted quota a current deployment is enforcing | this page cannot guarantee that; the current public docs do not publish a numeric realtime quota table |
What is published today
| Topic | Current public contract |
|---|
| WebSocket lifecycle | Connect, send SUBSCRIBE or UNSUBSCRIBE messages with a client nonce, then consume server-pushed updates |
| Initial state | Use REST for initial snapshots or current user state before relying on realtime updates |
| Failure signaling | Treat ACKNOWLEDGE.result.error and the documented realtime error surfaces as the published control-plane failure channel |
| Subscription behavior | The public docs describe how to connect and subscribe, but do not publish a numeric per-second or per-minute control quota table |
Current public contract
The current realtime source artifact does not publish numeric rate-limit values or tier tables. It publishes control-message shapes, acknowledgement semantics, feed families, and ordering fields, but not how many subscription-control messages per unit time are allowed.
Historical docs described per-account WebSocket rate limits for command traffic and said subscriptions were not rate limited. Those older command-oriented statements are not part of the current published AsyncAPI family, so do not treat them as the canonical contract for this Mintlify surface.
Generated AsyncAPI rendering is active, but the published source artifact still omits a numeric quota table. Design clients to:
- pace reconnect, subscribe, and unsubscribe loops instead of treating missing numeric publication as permission for unbounded bursts
- treat
ACKNOWLEDGE.result.error as the only published control-plane failure channel
- rely on reconnect and resubscribe behavior instead of assuming undocumented quota thresholds
- keep the “no numeric table published” fact explicit in your client docs and operational runbooks instead of inventing a constant from older materials
Relationship to REST limits
Realtime rate posture and REST rate posture are not interchangeable.
| Family | What is published |
|---|
| REST | Numeric request tiers, DDX-balance thresholds, and burst constants for the documented request-submission path |
| Realtime | Connection and message-shape rules without a current public numeric quota table |
Adjacent routes
Last modified on April 13, 2026