---
title: Console API Overview
description: "Introduction to the Statsig Console API for programmatically managing feature gates, experiments, dynamic configs, metrics, and project settings."
product: general
lang: en
token_estimate: 548
---
# Console API Overview

> For AI agents: a documentation index is available at [/llms.txt](/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

The Console API is the CRUD API for performing the actions available on console.statsig.com without using the web UI.

If you have feature requests, post them in the [Slack channel](https://www.statsig.com/slack).

## Base URL

`https://statsigapi.net`

## Authorization

All requests must include a Console API key in the `STATSIG-API-KEY` header. Create a key in [Project Settings](https://console.statsig.com/api_keys).

## Rate limiting

The Console API rate limits mutation requests (`POST`, `PATCH`, `PUT`, and `DELETE`). Most mutation endpoints share a quota per project across all Console API keys. The default quota is approximately 1,800 request attempts per 15-minute window. Limits can vary by project and endpoint. Segment endpoints use a separate quota.

Statsig also applies burst protection. A burst of requests can trigger rate limiting even when your project is below its 15-minute quota. Spread requests over time and limit concurrent requests.

The API returns `429 Too Many Requests` when a request exceeds either limit. Attempts rejected by this rate limiter also count toward the quota, so immediate retries can consume additional capacity.

When you receive a `429` response:

- Reduce request concurrency.
- Retry with exponential backoff and jitter: increase the delay after each retry and add a random delay to avoid simultaneous retries.
- Limit the number of retries to avoid repeatedly consuming your quota.

Contact [Statsig support](https://www.statsig.com/slack) to confirm your project's limits or discuss higher-volume requirements.

## API version

Statsig versions the Console API. Statsig guarantees that each version won't break existing usage; each new version introduces breaking changes. There is only one version: `20240601`. Statsig keeps the [OpenAPI spec](https://api.statsig.com/openapi/20240601.json) for this API version up-to-date.

Pass the version in the `STATSIG-API-VERSION` field in the header. This field is optional but becomes required in the future.