Quix Rate Limits
Quix does not publish a fixed numeric rate-limit table for its HTTP and SignalR APIs. The practical throughput of the Streaming Writer API (HTTP), Streaming Reader API (SignalR/WebSocket), and Portal API is bounded by the capacity of the underlying managed Kafka and Kubernetes resources provisioned for your Quix Cloud environment rather than by a per-key request quota. Authentication uses Personal Access Tokens (PATs); expired or invalid tokens return HTTP 401 (or an UnAuthorizedHubError on the SignalR hub).
Quix Rate Limits is the machine-readable rate-limit profile for Quix on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests and connections.
The profile also includes 3 backoff/retry policies defined and response codes documented for unauthorized.
Tagged areas include Stream Processing, Real Time, Kafka, Python, and Streaming Data.