How to Avoid Query Rate Limit Exceeded Errors in Your Project

Hi Juan I., 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> 👋

I see you're encountering rate limit issues with Mixpanel's API. Based on the knowledge sources, Mixpanel enforces rate limits to ensure system integrity and prevent a single project from monopolizing resources.

The Query API has a rate limit of 60 queries per hour and a maximum of 5 concurrent queries. When you exceed these limits, you'll receive a 429 response code indicating you've reached the rate limit.

There are two main approaches to reduce rate-limiting errors: 1. Spread your queries out over a longer period of time - Distribute your API calls more evenly throughout the hour.2. Consolidate multiple queries into a single query - For example, multiple queries filtering on a single property may be combined into a single segmentation query.Rate LimitsFor the Query API specifically, you'll need to manage your query frequency to stay within the 60 queries per hour limit. If you're running automated scripts or applications that make frequent API calls, consider implementing a queuing system that spaces out your requests.If you're an Enterprise customer and require higher limits for specific use cases, you might want to reach out to your Mixpanel representative to discuss your needs.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.