Red Hat Enterprise Linux · Rate Limits
Rhel Rate Limits
The RHEL APIs exposed by the Red Hat Hybrid Cloud Console (Insights, subscription management, patch, vulnerability, compliance) are authenticated via Red Hat service accounts or offline tokens. Red Hat does not publish per-second or per-minute rate-limit numbers for the console APIs; throttling is applied at Red Hat's discretion to protect shared infrastructure and is communicated through standard HTTP 429 responses with Retry-After hints when applied.
1 Limits
Throttle: 429
Red HatRHELHybrid Cloud ConsoleRate Limiting
Limits
Hybrid Cloud Console APIs account
see Hybrid Cloud Console docs
Red Hat does not publish per-second numbers; throughput is bounded at the platform level and surfaced via 429 with Retry-After when triggered.
Policies
Service Account Authentication
Programmatic access to Hybrid Cloud Console APIs uses Red Hat service accounts (OIDC client credentials) or offline tokens. Tokens scope which entitled subscriptions are visible and indirectly bound throughput.
Backoff With Retry-After
Clients should honor the Retry-After header on 429 responses and apply exponential backoff with jitter for sustained workloads.
Entitlement-Bound Visibility
API responses are scoped to the subscriptions and hosts entitled under the requesting account; quota effectively follows entitlement count rather than a flat per-key number.