Statsig Events API
The Statsig Events API handles the ingestion of event data from both client and server SDKs. It receives exposure events, custom events, and diagnostic data at the events.statsigapi.net endpoint. This data powers Statsig's experimentation analysis, product analytics, and metric computations. The Events API is optimized for high-throughput data ingestion, processing over a trillion events daily with high reliability and low latency, enabling real-time experiment monitoring and metric updates.
Statsig Events API is one of 17 APIs that Statsig publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.
Tagged areas include Analytics, Data Ingestion, Event, Logging, and Metrics. The published artifact set on APIs.io includes API documentation, an OpenAPI specification, and an AsyncAPI specification.
This API exposes 1 operation across 1 path, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against a single base URL, https://api.statsig.com/v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Statsig Events API declares
3 security schemes
for authenticating requests.
An API key is passed in the header as statsig-api-key (clientSdkKey).
An API key is passed in the header as statsig-api-key (statsigApiKey).
An API key is passed in the header as statsig-api-key (serverSecretKey).
clientSdkKey— Client-SDK Key that is safe to embed in mobile apps and front-end web applications. Created in Project Settings API Keys tab.statsigApiKey— API key for authentication. Use a Server Secret Key for secure server-side requests or a Client-SDK Key for client-side applications.serverSecretKey— Server Secret Key for secure server-side API access. Must only be used from trusted server environments and never exposed client-side.
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
Endpoints for logging custom events and exposure data from client-side applications.
Schemas 5
The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are StatsigUser_2 (10 properties), StatsigUser (10 properties), StatsigEvent_3 (5 properties), StatsigEvent_2 (5 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Statsig 12
Other APIs Statsig publishes across the network.
This is an independent, third-party profile of Statsig Events API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.