specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Red Hat Enterprise Linux
providerId: rhel
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: true
tags:
  - Red Hat
  - RHEL
  - Hybrid Cloud Console
  - Rate Limiting
description: >-
  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.
sources:
  - https://developers.redhat.com/api-catalog/
  - https://console.redhat.com/docs/api
responseCodes:
  throttled: 429
  serviceUnavailable: 503
headers:
  retryAfter: Retry-After
limits:
  - name: Hybrid Cloud Console APIs
    scope: account
    metric: varies
    limit: see Hybrid Cloud Console docs
    notes: >-
      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:
  - name: Service Account Authentication
    description: >-
      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.
  - name: Backoff With Retry-After
    description: >-
      Clients should honor the Retry-After header on 429 responses and apply exponential
      backoff with jitter for sustained workloads.
  - name: Entitlement-Bound Visibility
    description: >-
      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.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com