API Endpoint(s) and/or Zoom API Event(s) List the calendars in the user’s own calendarList
GET /calendars/users/{userIdentifier}/calendarList
Description
I am encountering a persistent 401 Unauthorized error when calling the listCalendarLists endpoint, even though my OAuth token is freshly generated and contains the required scopes.
API Endpoint: GET /v2/users/{userId}/calendar/calendarLists
Technical Details:
App Type: General User-managed OAuth App (Admin-approved for the account)
Scopes associated with the token: user:read:user meeting:read:list_meetings meeting:read:meeting meeting:read:summary meeting:read:past_meeting meeting:read:list_past_participants meeting:read:participant meeting:read:list_upcoming_meetings meeting:read:meeting_audio meeting:read:meeting_transcript cloud_recording:read:list_user_recordings cloud_recording:read:list_recording_files cloud_recording:read:meeting_transcript calendar:read:list_calendar_lists calendar:read:event calendar:read:list_events calendar:read:instance_event calendar:read:calendar_list calendar:read:calendar meeting:read:assets
How To Reproduce curl ‘``https://api.zoom.us/v2/calendars/users/me/calendarList?maxResults=250&minAccessRole=reader&showDeleted=false&showHidden=false’`` –header ‘Authorization: Bearer TOKEN’
Troubleshooting Steps Taken:
Verified the token is fresh and includes the calendar:read:list_calendar_lists scope in the response payload.
Tested with both the me context and the explicit userId.
Confirmed other endpoints (like /v2/users/me) work correctly with this same token, confirming the token itself is valid for the General API.
Confirmed “Calendar and Contact Integration” is enabled for the user/account. Google calendar connected.
The invalid token payload error is a bit classic when The token is technically valid but the calendar service isn’t seeing the users specific authorization since your other calls work fine it’s likely that the token needs to be generated with the opened and profile scopes included in the original handshake to bridge The gap to integrated Google data it’s also worth trying call with explicit user id instead of The me alias as the calendar endpoints can sometimes be finiky about The alias context if that doesn’t clear it up it might be a backend sync issue where zoom isn’t passing claims correctly in which case support would need that reqld to check your apps internal permissions.
Since both the me alias and the explicit userid are failing with a fresh token it’s likely that the issue isn’t with your req syntx but with the account level perms or the user managed apps installation context in some cases even if the token has the right scope it will throw a 401 if the user hasn’t finished the calander and contact integration setup within the zoom web portal specifically for the app you’re testing another possibility is a mismatch in the acc id if you’re working in a multi tenant or sub acc environment. Or it maybe a backend sync gap you should probably give these codes to zoom support to see what the issue exactly is.