Hi @Manuel2 , thank you, I will inspect as well and reach out to the respective team who is in charge of those scopes.
I have the exact same issue, Need to understand what role / permissions are to be added for the scopes to be visible.
I saw another thread with same issue and resolution was to update the roles in admin console.
I’m having this issue also, but my user is the Owner of the entire account, so I have all role permissions already. But I cannot get this scope working for the API to list meetings/recordings. Has anyone figured out how to resolve it?
Hi @dave6 @psharma4 @Manuel2 ,
Something that was not clearly documented is that now, certain scopes are available for only certain apps.
This scope, I see available for Server-to-Server and Account-Level apps, but not User-Managed.
S2S:
Admin Managed:
Same issue for me with meeting:read:admin
I am also not seeing these cloud permissions when trying to create a Server to Server OAuth application. Is it possible that the user I am using to try and create this application does not have the correct permissions in Zoom?
This is the error message I am getting
"message": "Invalid access token, does not contain scopes:[cloud_recording:read:list_user_recordings, cloud_recording:read:list_user_recordings:admin]."
However, I do not see either of these options available to select in the Scopes for my S2S OAuth application.
I only can see the following scopes:
| archiving:read:archive_files:admin | View an archiving recording | ||
|---|---|---|---|
| cloud_recording:read:list_account_recordings:admin | list account recording | ||
| cloud_recording:read:recording:admin | View a recording | ||
| cloud_recording:read:archive_files:admin | Read archiving recordings |
Hi @rguss , exactly the user info does not have the role permissions to see other user data. The account Owner will need to provision this setting for your Admin user via web portal User Management → Roles and then click the pencil icon next to the user role type they belong to:
1 Like
Thank you! I was able to update the permissions and connect to the API 
1 Like
Okay great to hear @rguss !
@gianni.zoom I’m having a similar issue which I’ve opened on a separate thread and I’m wondering if you can please take a look:
I’m trying to make requests to the following Zoom API endpoints:
/report/activities/report/operationLogs
To view:
Zoom Meeting API: Sign In/Sign Out Activities
Zoom Meeting API: Operation Logs
However, I’m encountering this error:
Request is unable to be processed at this time due to No permission.
The documentation mentions that specific granular scopes are needed, but I don’t see these scopes listed under the Report section in the Zoom app settings. I’ve already confirmed that my app has the report:read-admin scope, but I don’t see an option to add the necessary granular scopes.
We previously had the granular scopes, but I’m not seeing them any longer and am wondering what happened or what scopes we should be using instead?
When I click Add Scopes > Product > Report I see:
report:master report:read:admin and report_chat:read:admin.
Additionally, we’re hitting these API’s using an enterprise account.
How can I add these granular scopes to the app or did something about these API’s change? We appreciate your help. Thanks!
Hi @amp23 , what app type is this? S2S or general OAuth?
This is unexpected. Can you recall around when you noticed this change? If you have any evidence to support seeing the switch from granular back to legacy scopes that would be helpful. Additionally, I’m going to private message you directly for the following:
- dev email
- client id for app
- screenshots of scope you’re seeing
- API response
- zm-tracking-id from API response header
1 Like
Thank you so much for helping us look into this, we really appreciate your help @gianni.zoom , as does our mutual customer! We published our OAuth Application in March with granular scopes and this is the we’ve heard of it not working. The integration is working for customers who authenticated prior to August.
Our app is an OAuth 2.0 Application that was developed following the OAuth Instructions.
When our customer tries to authenticate using oauth, we’re getting the following message from a request made with a 400 Status Code: No permission.
Looking at our app that was published via the marketplace, I noticed both granular scopes are missing and unavailable to be added under the “Report” section.
I’m unable to add a screenshot, but on the left under product, I’ve selected “Report”. The options available are:
- View sub account’s report data
report:master
View report data
report:read:admin
View your team chat history report
report_chat:read:admin
For reference, we’re trying to hit this endpoint for operation and activity logs:
https://api.zoom.us/v2/report
Thank you again for your help! I’ve responded via private message and am posting here as well for others who may be looking at this in the future.
Hi @amp23 , I just asked for two more pieces of information in the private message. Thank you!
Hi @gianni.zoom,
We’ve responded to your previous PMs with more information, but we’re still hoping to make progress on this issue, as our integration has been broken for several weeks now, impacting our mutual customers.
To provide some context, this is a General App, and I’m unable to add granular scopes. However, when I create a new test General App, the required scopes are visible. Additionally, updating the scopes requires all users to reauthenticate, which we’d like to avoid.
Could you please advise on how we can get the new scopes applied to our existing app? Is building a new app the only solution?
Tagging @michael.zoom @ojus.zoom @elisa.zoom @chunsiong.zoom for further visibility.
Thank you!
Hi @amp23 , I responded to you a few days ago asking for the correct email as the one linked to your devforum account is not visible on the account.
I just followed up today in the private message as well. Thanks!
I was able to resolve this by filing a support ticket here and was helped by @elisa.zoom.
Posting what I learned in case it helps someone else in the future. The behavior I was experiencing is expected. Zoom transitioned from Classic Scopes to Granular Scopes in March. If you have an existing app using Classic Scopes, they will remain compatible, but it’s recommended to upgrade through the migration process in your OAuth application. To do so, you’ll need to create a new application. Additionally, any time you add a new scope, users will need to reauthorize. If you create a new app, the app must undergo the functional review process again. Granular Scopes are not available for classic apps.
I also encountered “no permission” errors from the Zoom API. In this case, ensure that the user authenticating has met the prerequisites outlined in the support section linked in the API documentation.
Support reference: Zoom Support Article
API Documentation: Zoom OAuth Scopes
Thanks for sharing what had happened with the reversion!