Mixpanel Daily Raw Data Export Event Limit Explained
how many events raw data export does Mixpanel support on a daily basis? kapa.ai
how many events raw data export does Mixpanel support on a daily basis? kapa.ai
Mixpanel’s Raw Data Export API is rate-limited to 60 queries per hour, 3 queries per second, and a maximum of 100 concurrent queries. However, there is no explicit limit on the number of events you can export per day; the practical limit depends on the number of queries you can make and the number of events returned per query (with a maximum of 100,000 events per query).
Assuming you use the maximum allowed (60 queries per hour × 24 hours = 1,440 queries per day), and each query returns 100,000 events, you could theoretically export up to 144 million events per day via the Raw Data Export API, provided your data and queries support this volume. Actual throughput may vary based on your data size and query structure. If you exceed these limits, you will receive a 429 error response from the API Mixpanel APIs: Rate Limits Event Export API - Export.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ 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! 📚
To pull a raw extract of user properties (user profiles) from Mixpanel via API, you should use the Engage API. This API allows you to export user profile data, including all user properties, in a structured JSON format.
How to Export User Properties via API
Sample cURL Request:
curl --request POST \
--url '[https://mixpanel.com/api/query/engage?project_id=YOUR_PROJECT_ID](https://mixpanel.com/api/query/engage?project_id=YOUR_PROJECT_ID)' \
--header 'accept: application/json' \
--header 'authorization: Basic YOUR_TOKEN' \
--header 'content-type: application/x-www-form-urlencoded'
- Replace YOUR_PROJECT_ID and YOUR_TOKEN with your actual project credentials.
Response Example:
{
"page": 0,
"page_size": 1000,
"results": [
{
"$distinct_id": 1,
"$properties": {
"$created": "2008-12-12T11:20:47",
"$email": "example1@[mixpanel.com](http://mixpanel.com)",
"$first_name": "Example1",
"$last_name": "Name1",
"$last_seen": "2008-06-09T23:08:40"
}
},
...
],
"session_id": "1234567890-EXAMPLE",
"status": "ok",
"total": 1
}
- The user profiles are in the results array, each with their properties under $properties.
Pagination:
If your project has many profiles, use the session_id and page parameters to paginate through results. Continue making requests with the same session_id and increment the page number until all profiles are retrieved Exporting Profiles Query Profiles.
Optional:
- Use the output_properties parameter to limit which properties are returned.
- You can also filter by cohort or use selectors for more targeted exports.
Python Example
You can also use the mixpanel-utils Python module:
```
from mixpanel_utils import MixpanelUtils
mputils = MixpanelUtils( 'ServiceAccountSecretHere', token='ProjectTokenHere', service_account_username='my-user.12345.mp-service-account', project_id=1695321, )
selector = '' # Add your selector if needed parameters = {'selector': selector} mputils.export_people('people_export.json', parameters)
This will export user profiles to a file in JSON format.
---
For more details, see the [Mixpanel Export Methods documentation](https://docs.mixpanel.com/docs/export-methods#exporting-profiles) and the [Engage API reference](https://github.com/mixpanel/docs/blob/main/reference/Query%20API/engage/engage-query.md).
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ 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! 📚
The workspace_id is an optional parameter for the Engage API (used for querying user profiles) and other Query API endpoints. According to the documentation, you should include the workspace_id as a request parameter if your project uses Data Views. In these cases, the workspace_id identifies the specific data view (workspace) you want to query within your project. For most standard projects without Data Views, workspace_id is not required—only project_id is mandatory when using a service account for authentication Query API Authentication.
The "EVENT ENDPOINT API" you mentioned is likely referring to the Raw Data Export API, which is used to export event data. Similarly, for projects with Data Views, you should include the global data view's workspace_id as a request parameter when exporting data Event Export API Authentication.
In summary: - workspace_id is required when your project uses Data Views. - For standard projects, it is optional and not needed unless specified.
The Engage API is the endpoint for querying user profiles, and the Raw Data Export API is the endpoint for exporting event data.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ 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! 📚
Based on the knowledge sources, the workspace_id parameter is required when your project uses Data Views. This applies to all Query API endpoints, including the Insights report API, Engage API, and Raw Data Export API. If your project does not use Data Views, workspace_id is optional and not needed—only project_id is required when using a service account for authentication.
To summarize: - workspace_id is required if your project uses Data Views. - For standard projects (without Data Views), workspace_id is optional and not required.
This is not limited to just the Insights report API; it applies to all relevant Mixpanel Query API endpoints when Data Views are in use Query API Authentication Event Export API Authentication.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ 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! 📚
If you are pulling data from the "All Project Data" (the global Data View) and not from any custom Data Views, you should include the global data view's workspace_id as a request parameter when using the Query API or Raw Data Export API. This is required for projects with Data Views, even if you are not using a custom Data View, but rather the default "All Project Data" view Query API Authentication Event Export API Authentication.
So, yes, you need to provide the workspace_id for the global data view ("All Project Data") in your API requests if your project has Data Views enabled.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.