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: CloudBees
providerId: cloudbees
generated: '2026-09-05'
method: searched
source: https://docs.cloudbees.com/docs/cloudbees-feature-management-rest-api/latest/introduction
created: '2026-05-04'
modified: '2026-09-05'
limit_count: 1
tags:
  - CI/CD
  - Feature Management
  - Rate Limiting
  - Throttling
description: >-
  CloudBees publishes exactly one API rate limit, and it is on the CloudBees Feature Management REST API.
  The CloudBees Unify Public API (api.cloudbees.io) documents no limits at all, and neither harvested Unify
  specification declares a 429 response on any operation.
limits:
  - name: CloudBees Feature Management REST API — per-IP throttle
    api: CloudBees Feature Management REST API
    scope: per-ip
    metric: requests_per_second
    limit: 1
    burst: null
    timeFrame: second
    status_on_exhaustion: 555
    headers: []
    documented: true
    source: https://docs.cloudbees.com/docs/cloudbees-feature-management-rest-api/latest/introduction
    note: >-
      "The API is rate limited to one request per second" based on the requester's IP address; requests over
      the limit receive HTTP 555. 555 is not a registered HTTP status code, so a generic client will classify
      it as an unknown 5xx — an agent must special-case it or it will retry straight back into the limit.
      No X-RateLimit-*, RateLimit-* or Retry-After headers are documented, so a caller cannot see how much
      budget remains or when to retry; the only safe strategy is to stay under one request per second.
undocumented:
  - api: CloudBees Unify Public API
    host: https://api.cloudbees.io
    finding: >-
      No rate limits published. openapi/cloudbees-unify-openapi.yml and
      openapi/cloudbees-unify-beta-openapi.yml declare only 200 and a default error response on all 65
      operations — no 429, no rate-limit headers, no quota. Recorded as an honest gap, not as "no limits
      exist": an undocumented limit is still a limit a caller will hit.
    checked: '2026-09-05'
  - api: CloudBees CI REST API
    finding: >-
      Self-hosted / customer-operated controllers. Throughput is a function of the customer's own
      installation, so there is no vendor-published limit to record.
  - api: CloudBees CD/RO REST API
    finding: Self-hosted / customer-operated servers; no vendor-published limit.
response_headers:
  published: false
  note: >-
    CloudBees publishes no rate-limit response headers on any surface. This is the runtime signal an agent
    actually needs, and none is available.
note: >-
  This file previously carried five scaffolded per-tier limits (10/100/1000 rpm across Free, Professional and
  Enterprise) plus X-RateLimit-* headers, written by the 2026-05-04 bulk sweep and marked method:generated.
  None of that was published by CloudBees; it has been replaced by the one real limit and an explicit record
  of what is undocumented.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com