Marketing Skills Directory Mixpanel API
Free
Free plan 1M events/mo. Growth starts at $0, then volume pricing ($100/mo at 1.5M events).
Free plan, 1M events/mo; API included
Basic
Service account username and secret via HTTP basic auth. Ingestion uses a project token. Pass project_id as a query parameter.
Event counts and segmentation
Funnels
Retention
User and group profiles
Raw event export
Pricing checked on 23 Oct 2026 · Pricing page · Docs
Description
Mixpanel has an ingestion API for sending events and profiles, and a Query API for pulling report data such as segmentation, funnels and retention. A separate export API returns raw events.
It suits agents and workflows that report on product usage or campaign-driven behaviour. Most read APIs use a service account with basic auth.
The Query API is tightly rate limited: 60 queries per hour and 5 concurrent. That is fine for scheduled reports and poor for chatty agents. Note that on the pricing page the Query API is not on the Free plan.
Key endpoints
GET /insights: data from a saved Insights reportGET /funnels: saved funnel reportGET /events: aggregate event counts
Example request
curl -u "SERVICE_ACCOUNT_USERNAME:SERVICE_ACCOUNT_SECRET" \
"https://mixpanel.com/api/query/insights?project_id=YOUR_PROJECT_ID&bookmark_id=YOUR_REPORT_ID"
Tech details
- API style
- REST
- Base URL
- https://mixpanel.com/api/query
- Rate limits
- Query API: 60 queries/hour, 5 concurrent. Raw export API: 60 queries/hour, 3/second, 100 concurrent. Per project.
- Official SDKs
- See docs
Use Cases
Event counts and segmentation
User and group profiles
Raw event export
Editor’s note What our review found
Editorial research, reviewed 23 Oct 2026. We read Mixpanel's pricing and API docs pages. We did not run live calls. This listing is not an endorsement.
Cost: the Free plan lists "Up to 1M events / month". The pricing page's plan table lists ingestion and export API access and Query API access as available on Free, Growth and Enterprise. Growth starts at $0 with 1M events included, and extra events are billed by volume (for example $100 a month at 1.5M events on yearly billing).
Credentials and data: use a service account username and secret (HTTP basic auth). Ingestion uses a project token. Project secret auth is the older method and is being phased out. Store credentials in a secret manager or environment variable, never in code or a plain-text file. Events and profiles can hold personal data, so consider GDPR and consent.
Good to know: choose the right region host (US, EU or India). The docs mark the older Segmentation endpoint as in maintenance mode and point new work to the Insights query, so the example uses that. Event ingestion is a separate host from the query API.