# Admin API: /teams/daily-usage-data omits removed members (still returned by filtered-usage-events) **URL:** \ **Category:** Bug Reports\ **Tags:** teams-enterprise\ **Created:** [July 12, 2026, 2:20pm UTC](https://forum.cursor.com/t/admin-api-teams-daily-usage-data-omits-removed-members-still-returned-by-filtered-usage-events/165528 "2026-07-12T14:20:59Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Misha\_Kav](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/misha_kav/32/114341_2.png) [@Misha\_Kav](https://forum.cursor.com/u/Misha_Kav)\ **Post date:** [July 12, 2026, 2:20pm UTC](https://forum.cursor.com/t/admin-api-teams-daily-usage-data-omits-removed-members-still-returned-by-filtered-usage-events/165528/1 "2026-07-12T14:20:59Z")
### Where does the bug appear (feature/product)? Somewhere else… ### Describe the Bug On a Team plan (Bearer admin API key), POST /teams/daily-usage-data returns no rows for a team member who was active in a past period but has since been removed — even for date ranges when they were active. The same member is still returned by POST /teams/filtered-usage-events and appears in the Analytics dashboard for the same range. So former members’ historical activity is unrecoverable from daily-usage-data while it remains available everywhere else. ### Steps to Reproduce Same API key, same past month M. Pick a member (“User A”) who was active in M and was later removed from the team. 1. POST /teams/filtered-usage-events {startDate, endDate} for M → User A is present (e.g. ~1,160 events), and every event is isHeadless:false (per docs: “made with a connected client” → IDE, not a background/headless agent). 2. POST /teams/daily-usage-data {startDate, endDate} for the same M → User A is absent. Adding page + pageSize returns only current members (still no User A). 3. GET /teams/members → User A has isRemoved: true. Also: filtered-usage-events with email= returns “Email not valid”, and the dashboard per-user filter for User A shows “Could not load analytics data” — so removed members can’t be queried per-user anywhere, yet they appear in bulk responses. ### Expected Behavior Per the docs, paginated daily-usage-data returns “all team members with a membership during the requested date range.” User A had a membership during M (confirmed by filtered-usage-events and teams/members), so they should be included — consistent with filtered-usage-events and the Analytics dashboard, which both still show them. Removing a member should not erase their historical usage from daily-usage-data. ### Operating System Other ### Version Information N/A — server-side Cursor Admin API ([api.cursor.com](http://api.cursor.com)), Team plan. Not IDE/CLI-specific. ### Additional Information Not an IDE-vs-CLI artifact: User A’s events are 100% isHeadless:false (your docs: “made with a connected client”). Impact: former members’ historical adoption/productivity data is permanently lost from the primary usage endpoint, even though they were billed and still appear in filtered-usage-events and the Analytics dashboard. ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [July 13, 2026, 12:27pm UTC](https://forum.cursor.com/t/admin-api-teams-daily-usage-data-omits-removed-members-still-returned-by-filtered-usage-events/165528/6 "2026-07-13T12:27:23Z")
Thanks for the report @Misha_Kav. This is a known issue, and I’ve linked your report to the internal bug report we have tracking this. ---
**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\ **Post date:** [August 10, 2026, 4:05pm UTC](https://forum.cursor.com/t/admin-api-teams-daily-usage-data-omits-removed-members-still-returned-by-filtered-usage-events/165528/10 "2026-08-10T16:05:18Z")
Hey @Misha_Kav, this is sorted on our side now. `/teams/daily-usage-data` includes members who were removed but had a membership during the requested range, so it lines up with `filtered-usage-events` and the dashboard again. It’s a server-side change, so nothing to update. Just re-run the query for the same range and the former members should show up. Let me know if anyone’s still missing.