Spot by Flexera · Rate Limits

Flexera Rate Limits

Spot.io / Flexera does not publish per-second numeric rate limits for the public Spot API at api.spotinst.io. Bearer-token authenticated requests are subject to standard 429 throttling and an X-Request-Id is returned for correlation. Bulk operations (large cluster updates, savings reports) may queue.

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

It captures 1 rate-limit definition, measuring varies.

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

Tagged areas include Autoscaling, Cloud Infrastructure, Cost Optimization, Kubernetes, and Spot Instances.

1 Limits Throttle: 429
AutoscalingCloud InfrastructureCost OptimizationKubernetesSpot InstancesRate Limiting

Limits

Spot API default throttle account/api-token
varies
not publicly published; standard 429/503 throttling applies

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter on 429/5xx and honor Retry-After when present.
Bulk Operation Queueing
Long-running operations (cluster scale-out, commitment optimization runs) are asynchronous; poll the operation endpoint rather than retry the originating request.
Per-Account Tokens
API tokens are scoped to the Spot account; rotate via the console; revoking a token deauthorizes immediately.

Sources