Statsig Console API
Official vendor OpenAPI document · agent-readyIdentity AuthAuthorizationapiKey269 EndpointsREST
For Agents
Programmatically list topline alerts, read topline alert. Covers 269 operations with apiKey authentication.
Use for: I need to topline alerts, I want to read topline alert, Search for topline alert events, Find all read topline alert event
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
The "Console API" is the CRUD API for performing the actions offered on console.statsig.com without needing to go through the web UI. If you have any feature requests, drop on in to our [slack channel](https://www.statsig.com/slack) and let us know. <br /><br /> <b>Authorization</b> <br /> All requests must include the **STATSIG-API-KEY** field in the header. The value should be a **Console API Ke. The API exposes 269 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Console API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Console API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fstatsig.com%2Fstatsig" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fstatsig.com%2Fstatsig" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Console API.
List Topline Alerts
Read Topline Alert
Create Autotune
Query and filter Console API records by parameters
Monitor Console API operational status and events
Use Cases
Patterns agents use Console API for, with concrete tasks.
★ Identity and Authentication Operations
Use the Console API to perform identity auth operations programmatically. The API provides 269 endpoints covering core functionality including list topline alerts, read topline alert, list topline alert events.
Call GET /console/v1/alerts to list topline alerts
Automated Console Management
Automate console operations by combining multiple Console API endpoints. Agents can read topline alert and then list topline alert events in a single workflow.
Call GET /console/v1/alerts/{id} to read topline alert, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Console API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'list topline alerts', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
269 endpoints — the "console api" is the crud api for performing the actions offered on console.
METHOD
PATH
DESCRIPTION
GET
/console/v1/alerts
List Topline Alerts
GET
/console/v1/alerts/{id}
Read Topline Alert
GET
/console/v1/alerts/{id}/events
List Topline Alert Events
GET
/console/v1/alerts/{id}/events/{eventId}
Read Topline Alert Event
GET
/console/v1/audit_logs
List Audit Logs
POST
/console/v1/autotunes
Create Autotune
GET
/console/v1/autotunes
List Autotune
POST
/console/v1/autotunes/{id}
Fully Update Autotune
GET
/console/v1/alerts
List Topline Alerts
GET
/console/v1/alerts/{id}
Read Topline Alert
GET
/console/v1/alerts/{id}/events
List Topline Alert Events
GET
/console/v1/alerts/{id}/events/{eventId}
Read Topline Alert Event
GET
/console/v1/audit_logs
List Audit Logs
POST
/console/v1/autotunes
Create Autotune
GET
/console/v1/autotunes
List Autotune
POST
/console/v1/autotunes/{id}
Fully Update Autotune
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Statsig Console API by hand means setting up its STATSIG-API-KEY header, navigating hundreds of console endpoints, and threading resource ids through alerts, autotunes and audit-log calls yourself. Through Jentic you install once, import the Console API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
The Console API puts resource ids in the URL path (/console/v1/alerts/{id}, /console/v1/alerts/{id}/events), so a rule can pin your agent to one alert: it can read that alert and its events and nothing else. You choose the operations it may call, so autotune changes are not included unless you add them.
Credential isolation
Your Statsig API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list topline alerts' or 'read audit logs', and Jentic returns the matching Console API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Console API through Jentic.
What authentication does the Console API use?
The Console API uses an API key passed in the `STATSIG-API-KEY` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I list topline alerts with the Console API?
Yes. Use the GET /console/v1/alerts endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Console API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I list topline alerts through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list topline alerts'. Jentic returns the matching Console API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Console API have?
The Console API exposes 269 endpoints covering console operations.
Can I limit what my agent is allowed to do with the Statsig Console API?
Yes. Because you run Jentic One yourself, your own rules decide which Console API operations and credentials the agent may use. Since the API carries resource ids in the URL path, such as /console/v1/alerts/{id} and /console/v1/alerts/{id}/events, you can pin the agent to a single alert so it only reads that alert and its events. You also choose the exact operations it may call, so write actions like creating or updating autotunes stay off limits unless you explicitly allow them.
GET STARTED