Invalid access token, does not contain scopes:[] when calling Deeplink API

API and Webhooks
1

Invalid access token, does not contain scopes:[] when calling Deeplink API with a user token.

I am developing user application that on backend exchanges auth_code for access_token and uses that access_token to create a deeplink when user authorizes the app.

It worked for a while but today I started to receive the following error:

{"code":4711,"message":"Invalid access token, does not contain scopes:[]."}

Looks like there is something wrong because the scope list is empty.
The URL: https://zoom.us/v2/zoomapp/deeplink

The app is in the development stage.
Those are scopes set for it on the portal:

  • user:read:user
  • zoomapp:inmeeting
  • zoomapp:inwebinar

I’ve searched the forum but cannot find an answer to an empty scopes for Deeplink API.

1 Like
2

@chunsiong.zoom , could you please maybe point me in the right direction? Can I somehow investigate that issue? I’ve noticed that there is another topic form yesterday that this Deeplink API suddenly stopped working.

3

When I run github sample zoomapps-sample-js, same issue happened.

4

Thx for the input. I’ve found another issue reported on Monday (Failed to get deeplink via https://zoom.us/v2/zoomapp/deeplink).

Looks like something happened on the Zoom backend that broke staff during weekend.

5

Yeah, I’m pretty sure that some weird things happened on the Zoom backend. This code has been working well for a while, and suddenly it broke.
I’m so disappointed, since our app has just been approved and published on Zoom marketplace.

7

Hi @pkowalik @synix521 @james11 , I will escalate this on your behalf. I will direct message you all for the following info:

  • recording reproducing behavior (you can record to Zoom and share link)

  • client id

  • dev email associated with credentials making API request

  • API response zm-tracking-id (found in the response headers)

Check notifications for the message.

8

Hi all,

Submitted for bug review (ZSEE-132377).

I will share updates as they become available.

9

Hi Gianni, do you have a public link I could use to follow/view ZSEE-132377? I’m one more person being impacted so am following for updates. Thanks

10

Hi @usersinbuckets @pkowalik @james11 @synix521 , this should have been fixed June 22nd, can you please confirm?

11

Yeah this one is fixed before you give this notice.
Thank you and the team!

1 Like
12

Thank YOU! Appreciate your communication to help us fix this.

13

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