all right, here's what support gave us:
We have an undocumented endpoint with our Query API /engage that can retrieve the distinct_ids in a cluster (programmatically).
However, with this Alias endpoint, it does not have a way to query multiple distinct_ids/aliases at once (it can only query one alias/distinct_id at a time).
Additionally, this endpoint is subject to the rate limits with our Query API (Formatted API) which can be found here: https://developer.mixpanel.com/reference/rate-limits so it may not work for your use case since you’re looking for a couple thousand users.
Note - here is an example request:
curl --request POST \
--url 'https://mixpanel.com/api/2.0/engage/aliases?project_id=YOURPROJECTID' \
--header 'Accept: application/json' \
--header 'Authorization: Basic BASE_64_ENCODED_API_SECRET' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data distinct_id=TheUUIDFromInternalDB
With the above in mind, I took a look at your account and I see it has the Data Pipelines package.
With the package, it has a People Pipeline which exports an “Identity Mapping Table” to see and query identity clusters from a Mixpanel Project: https://docs.mixpanel.com/docs/data-pipelines/schematized-export-pipeline#user-identity-resolution
My recommendation is to create a Schematized People Pipeline export to one of your data warehouses, and you can then use the identity mapping table going forward to find the clusters.
