Flightcontrol · Rate Limits

Flightcontrol Rate Limits

Flightcontrol does not publish specific numeric rate limits for its HTTP management API or deploy hooks in the public documentation. The Get Services endpoint is paginated (take defaults to 25, max 100), which bounds per-request payload size. Practical throughput is also governed by plan-level service caps and by the underlying AWS provisioning and deployment pipeline rather than by a documented requests-per-minute throttle. Specific per-endpoint limits are not reconciled in this artifact.

Flightcontrol Rate Limits is the machine-readable rate-limit profile for Flightcontrol on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring records and requests.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Deployment, PaaS, Infrastructure, DevOps, and Rate Limiting.

3 Limits Throttle: 429
DeploymentPaaSInfrastructureDevOpsRate LimitingQuotasThrottling

Limits

Get Services Page Size request
records
100
take query parameter defaults to 25 and is capped at 100 records per page.
HTTP Management API account
requests
see provider documentation
No numeric requests-per-minute limit is published; not reconciled.
Deploy Hooks environment
requests
see provider documentation
No numeric limit published; each call enqueues a deployment for an environment.

Policies

Pagination
List endpoints use skip/take pagination to bound response size.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 and honor any Retry-After header.

Sources