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.

Business capability
Product Telemetry Instrumentation BC-4280.10

Operations 4

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /log_event Log custom events for analytics · Log custom events #
Ask an LLM
“How do I send custom events to Statsig for experiment analysis?”
“Can I log several events with values and metadata in one request?”
Tell an agent
Log these events {events} with client time {clientTime}.
Record a batch of custom events {events} sent at {clientTime} ms since epoch.
GET /console/v1/events List recently logged events · List Events #
Ask an LLM
“What events has my project received recently?”
“Does the event list cover full history or just recent traffic?”
Tell an agent
List recently logged events across all event names.
Show page {page} of recent events, {limit} per page.
GET /console/v1/events/{eventName} See recent occurrences of one event · Get specific events #
Ask an LLM
“Is a specific event like checkout_complete actually arriving?”
“Can I inspect recent payloads for one event name?”
Tell an agent
Show recent {eventName} events.
Fetch the last {limit} occurrences of event {eventName}.
GET /console/v1/events/{eventName}/metrics Find metrics built on an event · Get metrics using event name #
Ask an LLM
“Which metrics are derived from a given event?”
“What would break if we stopped logging a particular event?”
Tell an agent
List the metrics that use event {eventName}.
Show metrics built from {eventName}, page {page}.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/statsig:events-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

statsig-events-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Statsig Events API
  version: '1.0'
  description: 'Operations tagged Events across 2 of this provider''s published API definitions: statsig-http-api-openapi.yml, statsig-events-api-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.statsig.com/v1
  description: Statsig API Server
- url: https://statsigapi.net
tags:


# --- truncated at 32 KB (58 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/statsig/refs/heads/main/openapi/statsig-events-api-openapi.yml