What is the rate limit of the Merge Identities API?

Hi Lois, 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> 👋

Based on the knowledge sources, there are different rate limits for different Mixpanel APIs, but I need to clarify which specific rate limit applies to the Merge Identities API.For the Simplified ID Merge API, there is no explicit rate limit mentioned specifically for identity merging operations. However, since identity merging happens through the Ingestion API when events contain both $device_id and $user_id properties, the general Ingestion API rate limits would apply: The Ingestion API has a rate limit of "2GB of uncompressed JSON/minute or ~30k events per second, measured on a rolling 1 minute basis" Rate Limits.For the Original ID Merge system that uses explicit $merge events, these events must be sent via the Import API endpoint ([https://api.mixpanel.com/import](https://api.mixpanel.com/import`)), as mentioned in the documentation Identity Merge. Therefore, the same Ingestion API rate limits would apply to these operations as well.If you're performing identity management operations at scale, Mixpanel recommends: - Using concurrent clients (10-20) sending batches of 2K events - Implementing exponential backoff with jitter when encountering 429 responses - Using gzip compression to reduce network trafficFor enterprise customers requiring higher limits for one-time backfills, Mixpanel suggests reaching out to your sales representative.

ℹ️ 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 number of user profiles that can be merged in one call depends on which ID Merge API system you're using: For the Simplified ID Merge API: - There is no limit on the number of $device_ids (anonymous IDs) that can be merged into a single $user_id Identity Merge APIs. - The merging happens automatically when events contain both $device_id and $user_id properties.For the Original ID Merge API: - There is a limit of 500 IDs that can be merged into a single ID cluster Identity Merge APIs. - Once this limit is reached, any new Distinct ID can no longer be merged into the same ID cluster, causing them to become orphaned (duplicate users) Migrating to Simplified ID Merge.For batch profile updates (not merging), the User Profile API imposes a limit of 2000 profile updates per request, with each individual update limited to a maximum of 1 MB.

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