Missing scopes for cloud recording API

API and Webhooks
1

Format Your New Topic as Follows:

API Endpoint(s) and/or Zoom API Event(s)
Get Meeting Recordings API endpoint

Description
Using a server-to-server OAuth Zoom app with account-level access, I’m attempting to retrieve meeting recording data, specifically a meeting’s transcript, via the Get Meeting Recordings API. However, I receive the following error:

{'code': 4711, 'message': 'Invalid access token, does not contain scopes:[cloud_recording:read:list_recording_files, cloud_recording:read:list_recording_files:admin].}

Unfortunately, these scopes aren’t available to my Zoom app. I’ve selected all the available granular scopes, but none of them match the required scopes for this API endpoint. The scopes available in my Zoom app are:

  • cloud_recording:read:list_account_recordings:admin
  • cloud_recording:read:recording:admin
  • archiving:read:archive_files:admin
  • cloud_recording:read:archive_files:admin

Is there a reason for the mismatch between what’s available for selection in my Zoom app vs what’s required by the API endpoint?

Error?

{'code': 4711, 'message': 'Invalid access token, does not contain scopes:[cloud_recording:read:list_recording_files, cloud_recording:read:list_recording_files:admin].}

How To Reproduce
*1. Enable the above cloud_recording scopes in a server-to-server OAuth Zoom app
*2. Using that Zoom app, call the Get Meeting Recordings API endpoint
*3. The request will fail with the invalid access token error.

2

Hi @brian.lim
Thanks for reaching out to us and welcome to our Zoom Developer Forum!
Are you still having issues finding the “cloud_recording:read:list_recording_files:admin”?
If so, please let me know and I am happy to look further into this
Cheers,
Elisa

3

Hi Elisa,

Thanks for the reply. Yes, I’m still having issues finding the scopes needed for this API:

  • cloud_recording:read:list_recording_files
  • cloud_recording:read:list_recording_files:admin

Thanks!
Brian

4

Thanks Brian,
I will send you a DM to follow up

5

To update this thread, the issue was that this user’s role did not have the right permissions enabled.

These permissions can be enabled in the Admin tab > user management > Role > Role settings

6

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.