API Endpoint(s)
/users
/report/users/{userId}/activities
/report/users/{userId}/meetings
Description
We are encountering issues with the Zoom API while attempting to identify inactive accounts for license optimization. Despite using the correct scopes and endpoints, key fields such as last_login, last_activity, last_meeting, and meeting_count return blank or zeroed values for all users, including those known to be actively using Zoom.
Use Case:
Our goal is to identify users who have not logged in or participated in meetings in over 2 years, to free up licenses for new users. We are also attempting to account for users who access Zoom through an LMS (Blackboard) via an LTI integration.
Issue Details
Blank or Zeroed Fields:
The last_login, last_activity, and last_meeting fields are blank for all users.
The meeting_count field always returns 0, even for active users hosting or attending meetings.
LMS/LTI Access:
Many users access Zoom through Blackboard via LTI. It appears this activity is not reflected in API responses.
Discrepancy Between GUI and API Reports:
The Zoom GUI (e.g., Sign In/Sign Out reports, User Management export) shows activity for some users whose corresponding API fields are blank.
How To Reproduce
Request Details:
Endpoint: /report/users/{userId}/activities
Headers:
Authorization: Bearer {token}
Query Parameters:
{
"from": "2022-01-01",
"to": "2024-01-01"
}
Authentication:
App Type: Server-to-Server OAuth
Scopes:
meeting:read:list_past_participants:admin
report:read:user_activities:admin
report:read:list_users:admin
user:read:user:admin
user:read:list_users:admin
Behavior:
All relevant fields (last_login, last_activity, last_meeting, meeting_count) return blank or zeroed values.
Questions
Are there known limitations with the last_login, last_activity, or meeting_count fields when using these endpoints?
Does the API exclude login or meeting activity conducted via LMS integrations using LTI?
Is there an alternative method to accurately capture activity for users accessing Zoom through LTI or mobile apps?
Has anyone successfully used these endpoints to identify inactive users over a specific timeframe?
Goal
We need a reliable way to determine which users are truly inactive (no logins or meetings in 2+ years) so we can deactivate their accounts and free up licenses. Any insights or guidance from the community would be greatly appreciated.