Granular scopes: Specification change of Scope setting for creating Oauth apps on the Developer site

[hirosaka]

-Request Details

In the Scope settings (detailed settings after 21.March,Granular scopes) when creating an OAuth application.

Permissions granted to OAuth app (before 21.March, Classic scopes)
meeting:read
meeting:write
chat_channel:write
chat_message:write
contact:read

How should we select the one that corresponds to the above authority?
Please tell me how to select the one corresponding to the above authority.
From the error message, we think that the authorization corresponding to contact:read has not been granted.
I think that the authorization corresponding to contact:read may not have been granted.

-Occurrence-.

Create an OAuth app (UserManaged) on the zoom developer site, then,
POST request to “https://zoom.us/oauth/token” to obtain an access token

Using the token, make a GET request to “”,
Make a GET request to “https://api.zoom.us/v2/contacts” to confirm the user ID.

At the time of the GET request, the following message will appear.
“code”: 4711,
“message”: “Invalid access token, does not contain scopes:[contact:read:list_contacts, contact:read:list_contacts:admin].”

-Possible causes

No authorization is attached to the access token of the OAuth app.

Although there is a screen to grant authorization in the OAuth app creation flow,
However, due to a specification change in zoom’s Scope setting, it seems that the same authorization as before 21.March cannot be selected.
The same authorization as before 21.March is not available due to the specification change of zoom scope setting.

[Jonathan_Champ]

User Managed OAuth apps don’t use “:admin” scopes, so the granular scope you need to add is contact:read:list_contacts

[hirosaka]

Thank you for your response

I understand that the scope of granularity that needs to be added is contact:read:list_contacts

However, the issue here is that contact:read:list_contacts
is not found when selecting the SCOPE in the OAUTH app creation flow.

I have been reading various topics on this site for the past week or so,
I believe there are many similar questions.

“code”: 4711,.
“message”: “Invalid access token, does not contain scopes:.”

Although the type of authorization is different, we believe that this is a case where the required SCOPE cannot be selected (not found) depending on the API being used.
I think that this is the case.

[Jonathan_Champ]

That makes sense. If the API call is telling you to grant a scope that is not in the list of available scopes, then it’s a bug.

Maybe a Developer Advocate like @virginie.zoom can escalate this issue. (Sorry for the @, but I’m not sure the best way to ask for help)

[virginie.zoom (Virginie)]

Hi Jonathan and Hirosaka,

No worries at all! As a member of the App Marketplace Specialist team, I collaborate with third-party developers to help with their app submissions to the Zoom Marketplace. I’d be happy to tag one of my peers here to better assist with your questions.

@donte.zoom @MaxM @gianni.zoom Can you please help here?

[gianni.zoom (Gianni)]

Hi @hirosaka @Jonathan_Champ ,

These are the presently available granular scopes: Integrations - Granular scopes

Please click on the API from this list to see which are available for the available endpoints. If it is not listed here yet, this means it is not yet in production and published for use.

Please also not the Cloud Recording granular scopes should be present, but there is a bug preventing their visibility. This is being worked on and should be fixed soon (ZOOM-696701).