statsig · Rate Limits

Statsig Rate Limits

Statsig publishes rate limits on the Console API for mutation requests, throttled per project. Mutation calls are bounded by both a short-window (~100 requests / 10 seconds) and a longer-window (~900 requests / 15 minutes) ceiling; over-limit responses return HTTP 429. Read-side flag and config evaluations on the SDK / HTTP APIs are not published as numeric per-second limits and are governed by fair-use against the project's metered-event entitlement.

3 Limits Throttle: 429 Quota: 429
Rate LimitingFeature FlagsExperimentationConsole API

Limits

Console API mutations (short window) project
requests_per_10_seconds · second
100
Approximately 100 mutation requests per 10 seconds, per project. 429 returned on breach.
Console API mutations (long window) project
requests_per_15_minutes · minute
900
Approximately 900 mutation requests per 15 minutes, per project. 429 returned on breach.
Flag and config evaluations (SDK / HTTP API) project
varies
unlimited under fair use; metered against monthly event entitlement
No published numeric per-second cap; capacity is bounded by the plan's metered-event allowance.

Policies

Per-Project Scoping
Console API throttles are calculated per project rather than per API key, so concurrent keys for the same project share the budget.
Mutation vs Read
Documented numeric limits apply to mutation (write) endpoints on the Console API. Read-only evaluation traffic is governed by event quotas in the plan, not request-rate ceilings.
API Versioning
Clients should send STATSIG-API-VERSION (e.g. 20240601) to pin behavior; STATSIG-API-KEY authenticates requests against the project budget.
Backoff
On 429, clients should back off and retry with jitter; aggregate writes from a single project to avoid bursts that cross the 10-second window.

Sources