The API Report CardAPI Index
Mixpanel

Mixpanel API

Product Analytics / Behavioral Analytics · mixpanel.com

Mixpanel's APIs are public and self-serve: ingestion, query, raw export, Lexicon, cohorts, and GDPR endpoints, documented at developer.mixpanel.com. Ingestion scales to roughly 30k events per second, but the Query and Raw Export APIs cap at 60 queries per hour, which throttles large syncs.

Last verified: July 2026Software & Data Tools
API GRADE
A
VERIFIED JUL 2026

SCORECARD

ExistenceGOODDocumented HTTP APIs span ingestion, queries, raw export, Lexicon schema governance, cohorts, dashboards, and GDPR deletion.
AccessGOODFully self-serve with per-project Service Accounts; the 60 query per hour ceiling only moves via sales escalation.
CoverageGOODEvents, user profiles, groups, funnels, retention, cohorts, and annotations are all reachable programmatically.
AuthGOODScoped Service Accounts are the recommended auth; legacy Project Secrets still work but are deprecated.
Docs & DXGOODMaintained SDKs in Python, Node, Ruby, PHP, Java, and Go, Postman collections, and an llms.txt OpenAPI index for AI agents.
StabilityGOODDeprecations are signposted: Project Secrets remain functional while Service Accounts replace them as the standard.
MORE FROM THE REPORT CARD
Supergood: Mixpanel shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

Mixpanel scores A on the API Report Card. Mixpanel's APIs are public and self-serve: ingestion, query, raw export, Lexicon, cohorts, and GDPR endpoints, documented at developer.mixpanel.com. Ingestion scales to roughly 30k events per second, but the Query and Raw Export APIs cap at 60 queries per hour, which throttles large syncs.

Tried to integrate with Mixpanel?
SOURCES
Query API rate limit is brutally low, 60 queries/hour and only 5 concurrent, and Mixpanel publicly states it cannot be increased except via sales escalation for enterprise one-time backfills community.mixpanel.com
Raw Data Export API is capped at 60 queries/hour and 3 queries/sec, which makes syncing large historical date windows take days and routinely returns 429s developer.mixpanel.com
Bulk export pagination is fragile for large date ranges, community reports of partial data, timeouts, and missing events when exporting millions of records community.mixpanel.com
Integrations that issue 4-5 background API calls per user action can hit the 60/hour ceiling after only ~10 operations, then block until the next hour docs.y42.com
Project Secret auth is deprecated but still in active use in older client code; migrating to Service Accounts requires a coordinated rotation developer.mixpanel.com
Rate-limit response is a bare 429 with no published Retry-After contract; clients must implement custom backoff community.mixpanel.com
GDPR/Data Deletion API is hard-capped at 1 request/second, making bulk deletion compliance jobs slow for large user bases developer.mixpanel.com
Documentation is split across developer.mixpanel.com (API reference), docs.mixpanel.com (product docs), and community.mixpanel.com (Q&A) with overlapping and occasionally inconsistent guidance docs.mixpanel.com
Pricing model shifted from MTU (monthly tracked users) to event-based billing in Feb 2026, opaque to forecast, and overages on the Growth plan ($0.28 per 1,000 events above 1M) compound quickly for high-volume apps openpanel.dev
Free plan limit is enforced by blocking access to reports until the user upgrades or waits for the monthly reset, not by graceful overage billing, surprises small teams usercall.co
Enterprise plans start around $14,000/year with SSO and advanced features gated behind that tier, small/mid teams pay disproportionately for governance vendr.com
November 2025 security incident: Mixpanel was breached and downstream customer data (including OpenAI API platform user profiles) was exposed via Mixpanel-exported data cybernews.com
Mixpanel breach discussed on Hacker News with customer concerns about what data Mixpanel actually receives vs. what was supposed to be sent news.ycombinator.com
Learning curve is steep for non-analyst users despite Mixpanel positioning itself as accessible; building accurate funnels and cohorts requires understanding of event taxonomy prettyinsights.com
Session Replay and Experiments are newer add-ons and not yet at feature parity with FullStory or LaunchDarkly respectively userpilot.com
Migration cost is high: historical event data does not transfer cleanly to competitors, locking customers into Mixpanel for retroactive analysis even if they switch going forward posthog.com