From 5c6987e2a483487e9244feed8087c2e2f4dfd8e1 Mon Sep 17 00:00:00 2001 From: kurbycchua <50901466+kurbycchua@users.noreply.github.com> Date: Thu, 19 Mar 2026 11:13:52 +0800 Subject: [PATCH] Update query-api.md Update old text which is confusing The query endpoints should serve as the starting point for exporting user information from Mixpanel. This is done through the /engage endpoint. See the Export section for information on exporting event data. to The query endpoints should serve as the starting point for exporting information from Mixpanel. For example, exporting user profiles is done through the /api/query/engage endpoint. See the Export section for information on exporting event data. per slack: https://mixpanel.slack.com/archives/C050U6CQRLZ/p1773882761502069 --- reference/Query API/query-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reference/Query API/query-api.md b/reference/Query API/query-api.md index 5569f37587..ad07a9ec59 100644 --- a/reference/Query API/query-api.md +++ b/reference/Query API/query-api.md @@ -9,7 +9,7 @@ privacy: --- The Query API allows you to obtain the same calculated and formatted results that you see from a report in our web app. -The query endpoints should serve as the starting point for exporting user information from Mixpanel. This is done through the /engage endpoint. See the Export section for information on exporting event data. +The query endpoints should serve as the starting point for exporting information from Mixpanel. For example, exporting user profiles is done through the /api/query/engage endpoint. See the Export section for information on exporting event data. The Mixpanel Query API endpoints can: