Stigg · Rate Limits

Stigg Rate Limits

Stigg documents that the GraphQL and REST APIs are rate limited per endpoint, but the published rate-limits page references a separate per-endpoint table that was not directly accessible during reconciliation. Limits are enforced per API key. This artifact captures the policy surface; specific per-endpoint numbers should be sourced from the live docs.

1 Limits Throttle: 429

FinOpsPricingBillingEntitlementsUsage-Based BillingSaaSRate Limiting

Limits

GraphQL and REST API Rate Limits api-key

varies

see https://docs.stigg.io/docs/rate-limits for per-endpoint limits

Stigg publishes per-endpoint rate limits referenced from the GraphQL rate-limits documentation. Limits scope to the API key.

Policies

Per-Endpoint Limits

Stigg sets distinct rate limits per endpoint rather than a global account ceiling; consult the per-endpoint table in the rate-limits documentation.

Backoff Strategy

Clients receiving HTTP 429 should back off and retry; exponential backoff with jitter is recommended.

Sources

https://docs.stigg.io/docs/rate-limits