How to Use Raw Data Export API Without Setting a Limit Parameter to Retrieve All Data for a Date Range
Use Raw Data Export API if we do not set limit parameter. we can get all of data during the date we set?
Use Raw Data Export API if we do not set limit parameter. we can get all of data during the date we set?
Hi Auston T., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
Let me check the knowledge base for you again. One moment! 📚
You can use the Raw Event Export API to get all events for a given date range, but there are some important limits and practical constraints.
1. Getting “all data” for a date range
from_date and to_date are required and define the inclusive date range. [Export methods; Export API]
The response is JSONL (one event per line) and contains raw events as stored in Mixpanel. [Export methods]
The docs describe limit as:
“Use this parameter if you want to limit the max number of events to be returned. Value cannot be over 100000.” [Export API]
They do not explicitly state what happens if you omit limit (no documented default, no explicit guarantee that all events are returned), so I cannot confirm from the sources that omitting limit always returns every event in that range.
2. Documented limits
From the provided docs, the explicit limits for the Raw Event Export API are:
Rate limits:
60 queries per hour
3 queries per second
100 concurrent queries
If exceeded, you get HTTP 429. [Raw export rate; API rate limits; Project migration guide]
Per-request limit:
If you use limit, it cannot be over 100,000 events. [Export API]
The sources you provided do not mention:
Any hard cap on total bytes / file size for a single export response.
Any absolute maximum number of events per request when limit is omitted.
Because that is not documented in these sources, I can’t state a specific data-size limit beyond the limit ≤ 100000 rule when you set it.
3. Practical guidance from docs
Mixpanel’s own sample script suggests keeping each export request to roughly 1–2M events to keep files manageable, and using multiple date ranges when volumes are high. [Varied date ranges script]
You can run many requests in parallel up to the rate limits above to cover large historical ranges. [Varied date ranges script; API rate limits]
Summary:
You can export all data for a date range by calling the Raw Event Export API over that range (and splitting into multiple requests if needed), but the docs you provided only guarantee rate limits and the limit ≤ 100000 rule; they do not clearly document a default limit or a hard response size cap when limit is omitted.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Let me check the knowledge base for you again. One moment! 📚
Let me check the knowledge base for you again. One moment! 📚
Let me check the knowledge base for you again. One moment! 📚
You should filter on the top-level event field, not on properties[...], when you want to include or exclude specific event names.
The Raw Event Export API defines:
event (top-level) as “The event or events that you wish to get data for” via the event query parameter. [Export API]
where uses segmentation expressions, which operate on fields like event and properties["..."]. [Segmentation expressions]
So to exclude events by name, use:
--data-urlencode 'where=event != "Event A" and event != "Event B"'
properties["..."] is for event properties, not the event name itself.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.