CloudBees · Rate Limits
Cloudbees Rate Limits
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.
Cloudbees Rate Limits is the machine-readable rate-limit profile for CloudBees on the APIs.io network, in the API Commons Rate Limits shape.
It captures 1 rate-limit definition, measuring requests_per_second.
Limit state is signalled in the published and note response headers.
Tagged areas include CI/CD, Feature Management, Rate Limiting, and Throttling.
1 Limits
publishednote
Transcribed from the provider's documentation on 2026-09-05 — docs.cloudbees.com/docs/cloudbees-feature-management-rest....
View Source
CI/CDFeature ManagementRate LimitingThrottling
Limits
CloudBees Feature Management REST API — per-IP throttle per-ip
1
"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.
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.