# Failed to get deeplink via https://zoom.us/v2/zoomapp/deeplink

**URL:** <https://devforum.zoom.us/t/failed-to-get-deeplink-via-https-zoom-us-v2-zoomapp-deeplink/111629>\
**Category:** Zoom Apps\
**Created:** [June 10, 2024, 9:56am UTC](https://devforum.zoom.us/t/failed-to-get-deeplink-via-https-zoom-us-v2-zoomapp-deeplink/111629 "2024-06-10T09:56:35Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![james11](https://avatars.discourse-cdn.com/v4/letter/j/e5b9ba/32.png) [@james11](https://devforum.zoom.us/u/james11)\
**Post date:** [June 10, 2024, 9:56am UTC](https://devforum.zoom.us/t/failed-to-get-deeplink-via-https-zoom-us-v2-zoomapp-deeplink/111629/1 "2024-06-10T09:56:35Z")

</div>

Hi Zoom team,  
@MaxM @michael.zoom  
On behalf of AhaSlides development team, I’ve successfully published an Zoom app to the marketplace, named **AhaSlides** , on last Friday (Jun 07, 2024).

Here is the link to the app on marketplace: [App Marketplace](https://marketplace.zoom.us/apps/dkSZ5rgQTrmPRKS0GJcjNg)

The app has been running well through the weekend. And it was thoroughly tested and approved by Zoom reviewers.

All of the sudden, it has just broken when an user trying to login AhaSlides within Zoom App. It failed when calling the API `v2/zoomapp/deeplink` to get return to Zoom client after successfully authenticated with AhaSlides account.  
This bug is happening to all users, so in a nutshell, AhaSlides app is unusable at the moment.

Here is the request from our backend to Zoom API:

```auto
POST /v2/zoomapp/deeplink
Authorization: Bearer eyJzdiI6IjAwMDAwMSIsImFsZyI6IkhTNTEyIiwidiI6IjIuMCIsImtpZCI6IjZlOTBjNTk5LWJlYzQtNGVlNC1iMzBlLWNiOGI4Zjc0MGNhYiJ9.eyJ2ZXIiOjksImF1aWQiOiJkYWU4MWQxN2YwMWQ5OTQwZmQ2ZTlhNTRjOTc3YzJmMyIsImNvZGUiOiJjczh3UXNqeGNudHRwMkZfNS1pVEFLd3ZSLWo4b3NSSHciLCJpc3MiOiJ6bTpjaWQ6REdyM2l3bFNET21mUGxYMndkZ2F3IiwiZ25vIjowLCJ0eXBlIjowLCJ0aWQiOjAsImF1ZCI6Imh0dHBzOi8vb2F1dGguem9vbS51cyIsInVpZCI6ImhieV9KRTVzUkZTang3U2x0Y1pSMGciLCJuYmYiOjE3MTgwMTE3ODgsImV4cCI6MTcxODAxNTM4OCwiaWF0IjoxNzE4MDExNzg4LCJhaWQiOiJUM2NYeEY4SFE1R21DM01YazliSmJBIn0.frM_CmIBqRYixOjJ667WElj11nPl20QZsQXmjX8RAkZspZGnTrmx8-khhwsb7aYRR7GFMgDE5bD-m9pJjNL4Qw

```

And the returned response:

```auto
data: {
  code: 4711,
  message: 'Invalid access token, does not contain scopes:[].'
}

```

The application scopes that I registered is only `zoom:inmeeting`, nothing else. Why calling this API are trying to compare with `scopes: []` ? So confusing ?

I don’t know why this happened. Because this was running fine before.

Please help us as soon as possible, since the app is already on Marketplace.

---

<div class="post-metadata">

**Author:** ![pkowalik](https://avatars.discourse-cdn.com/v4/letter/p/848f3c/32.png) [@pkowalik](https://devforum.zoom.us/u/pkowalik)\
**Post date:** [June 12, 2024, 1:10pm UTC](https://devforum.zoom.us/t/failed-to-get-deeplink-via-https-zoom-us-v2-zoomapp-deeplink/111629/2 "2024-06-12T13:10:53Z")

</div>

Hi James, any news on that?  
We have similar issue: [Invalid access token, does not contain scopes:[] when calling Deeplink API](https://devforum.zoom.us/t/invalid-access-token-does-not-contain-scopes-when-calling-deeplink-api/111634)

---

<div class="post-metadata">

**Author:** ![james11](https://avatars.discourse-cdn.com/v4/letter/j/e5b9ba/32.png) [@james11](https://devforum.zoom.us/u/james11)\
**Post date:** [June 12, 2024, 1:27pm UTC](https://devforum.zoom.us/t/failed-to-get-deeplink-via-https-zoom-us-v2-zoomapp-deeplink/111629/3 "2024-06-12T13:27:45Z")

</div>

Thanks for your reply.  
Unfortunately, the issue remains. And I still don’t understand why this happened.  
This issue happened on your side too, so probably something broken on the zoom backend side.

Let’s wait for them… and hope

---

<div class="post-metadata">

**Author:** ![james11](https://avatars.discourse-cdn.com/v4/letter/j/e5b9ba/32.png) [@james11](https://devforum.zoom.us/u/james11)\
**Post date:** [June 12, 2024, 1:29pm UTC](https://devforum.zoom.us/t/failed-to-get-deeplink-via-https-zoom-us-v2-zoomapp-deeplink/111629/4 "2024-06-12T13:29:46Z")

</div>

The strange thing is, some apps (Kahoot, Slido to name a few) on the marketplace still able to get the deeplink after successfully authorized.

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [June 13, 2024, 3:02am UTC](https://devforum.zoom.us/t/failed-to-get-deeplink-via-https-zoom-us-v2-zoomapp-deeplink/111629/6 "2024-06-13T03:02:24Z")

</div>

Hi all, currently investigating!

> [@Invalid access token, does not contain scopes:\[\] when calling Deeplink API](https://devforum.zoom.us/t/invalid-access-token-does-not-contain-scopes-when-calling-deeplink-api/111634/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.

---

<div class="post-metadata">

**Author:** ![james11](https://avatars.discourse-cdn.com/v4/letter/j/e5b9ba/32.png) [@james11](https://devforum.zoom.us/u/james11)\
**Post date:** [June 14, 2024, 7:11am UTC](https://devforum.zoom.us/t/failed-to-get-deeplink-via-https-zoom-us-v2-zoomapp-deeplink/111629/7 "2024-06-14T07:11:55Z")

</div>

Hi @gianni.zoom , sorry for late reply,

Here are general information of our application:[REDACTED]

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [June 14, 2024, 8:28pm UTC](https://devforum.zoom.us/t/failed-to-get-deeplink-via-https-zoom-us-v2-zoomapp-deeplink/111629/8 "2024-06-14T20:28:00Z")

</div>

H i @pkowalik @james11 , submitted for bug review (ZSEE-132377).

I will share updates as they become available.
