# \[Security Update\] No token values in URL query parameters

**URL:** <https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782>\
**Category:** API and Webhooks\
**Created:** [November 14, 2022, 11:57pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782 "2022-11-14T23:57:26Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![eugenem](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/eugenem/32/39086_2.png) [@eugenem](https://devforum.zoom.us/u/eugenem)\
**Post date:** [November 16, 2022, 9:01pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/21 "2022-11-16T21:01:57Z")

</div>

We also just noticed this accidentally in an email digest and trying to evaluate the amount of work we need to do urgently. I won’t be surprised that many people are still unaware about this upcoming breaking change.

---

<div class="post-metadata">

**Author:** ![shariq.torres](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shariq.torres/32/39899_2.png) [@shariq.torres](https://devforum.zoom.us/u/shariq.torres)\
**Post date:** [November 16, 2022, 9:30pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/22 "2022-11-16T21:30:28Z")

</div>

JWT is not affected. This only applies to the Zoom API endpoints, basically all of the endpoints that are on this page – [Introduction to Zoom API](https://marketplace.zoom.us/docs/api-reference/introduction/)

---

<div class="post-metadata">

**Author:** ![eugenem](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/eugenem/32/39086_2.png) [@eugenem](https://devforum.zoom.us/u/eugenem)\
**Post date:** [November 16, 2022, 9:47pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/23 "2022-11-16T21:47:48Z")

</div>

@shariq.torres could you clarify if this endpoint is also affected?

`https://{{base-domain}}/rec/download/{{path-to-file-download}}?access_token={{JWT-token}}`

> **[Zoom Meeting API](https://marketplace.zoom.us/docs/api-reference/zoom-api/methods/#operation/recordingGet)**
>
> API Reference for /api-reference/zoom-api/methods

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [November 16, 2022, 11:05pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/24 "2022-11-16T23:05:34Z")

</div>

@eugenem,

> [@shariq.torres](#):
>
> we are removing the ability to set the access tokens, refresh tokens and revoke tokens in the URL query parameters.

Yes, it is my understanding that endpoint would be affected as the access token is being set in the query parameter.

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [November 16, 2022, 11:10pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/25 "2022-11-16T23:10:19Z")

</div>

@Alyssa,

> [@Alyssa](#):
>
> Yes, I do use APIs. What do I do now?

For any API request in which you are setting the **access token** , **refresh token** , or **revoke token** in the URL query parameters, you should update those API calls to set the token values in the **Authorization header** and **NOT** the **HTTP query parameters**.

---

<div class="post-metadata">

**Author:** ![shariq.torres](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shariq.torres/32/39899_2.png) [@shariq.torres](https://devforum.zoom.us/u/shariq.torres)\
**Post date:** [November 17, 2022, 12:30am UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/26 "2022-11-17T00:30:09Z")

</div>

Most definitely this endpoint is affected. All of the endpoints that [here](https://marketplace.zoom.us/docs/api-reference/introduction/) will need to send the access token in request headers. There are a couple of endpoints for the Meeting, Phone, and Chat APIs that deal with downloading recordings/transcripts. Even those endpoints that explicitly call out the access token as a query parameter, you will still need to make sure that the access token is in the request headers.

---

<div class="post-metadata">

**Author:** ![Anand\_Vyass](https://avatars.discourse-cdn.com/v4/letter/a/5e9695/32.png) [@Anand\_Vyass](https://devforum.zoom.us/u/Anand_Vyass)\
**Post date:** [November 17, 2022, 5:24am UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/27 "2022-11-17T05:24:16Z")

</div>

Hope this will help to someone.  
I followed this link to use the new authorisation header to generate ZAK for start meeting,

> **[Authorization](https://marketplace.zoom.us/docs/sdk/native-sdks/auth/#generating-zoom-access-token-zak)**
>
> The Zoom Developer Platform is an open platform that allows third-party developers to build applications and integrations upon Zoom’s video-first unified communications platform.

---

<div class="post-metadata">

**Author:** ![ckarpyszyn2](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ckarpyszyn2/32/40279_2.png) [@ckarpyszyn2](https://devforum.zoom.us/u/ckarpyszyn2)\
**Post date:** [November 17, 2022, 3:44pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/28 "2022-11-17T15:44:43Z")

</div>

The announcement you linked to says a date to be determined and that the changes are not required and will not affect production. If this page is to be trusted for announcements on breaking production changes, it needs to be clearly updated for us to be able to action on.

> Updated: February 23, 2022

> As part of our continued efforts to improve security for Zoom OAuth App Types using Authorization Flow, we released three new security features. These features go into effect on May 16, 2021. They are recommended, but not required, and will not affect your existing OAuth apps in production.

> At a date to be determined, we will make these features mandatory. We will notify you in advance of this date.

This will break and impact Zoom users using our app in production, and the notice period from this forum post is too short. We will need more time to make sure this does not disrupt and disappoint our Zoom customers.

---

<div class="post-metadata">

**Author:** ![John\_smith\_1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/john_smith_1/32/38241_2.png) [@John\_smith\_1](https://devforum.zoom.us/u/John_smith_1)\
**Post date:** [November 17, 2022, 3:48pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/29 "2022-11-17T15:48:19Z")

</div>

@shariq.torres It does not make sense to make such a huge change without a proper announcement. The document you shared clearly says that "the changes are not required and will not affect production.  
I am kindly asking you to figure this out and give some extra time to avoid a potential chaos.

---

<div class="post-metadata">

**Author:** ![bill.cherne](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bill.cherne/32/43097_2.png) [@bill.cherne](https://devforum.zoom.us/u/bill.cherne)\
**Post date:** [November 17, 2022, 5:04pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/30 "2022-11-17T17:04:29Z")

</div>

@shariq.torres what is the latest update? Will the changes still go into effect on November 19th? I know you claim that notices were sent out in the spring, however, it is obvious that your message was not clearly received. Can this breaking change be pushed out until the end of the year to give developers more time to update their integrations?

Looking forward to your update.

---

<div class="post-metadata">

**Author:** ![eugenem](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/eugenem/32/39086_2.png) [@eugenem](https://devforum.zoom.us/u/eugenem)\
**Post date:** [November 17, 2022, 5:33pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/31 "2022-11-17T17:33:30Z")

</div>

@shariq.torres unfortunately this change will break a key feature in our app. We are currently using “video download URL + token” as a media source on the client. We’re investigating an alternative approach that involves javascript and results in CORS errors. We’ll need more time to get this implemented.

Any updates on whether you can extend the timeline to give developers more time?

---

<div class="post-metadata">

**Author:** ![ckarpyszyn2](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ckarpyszyn2/32/40279_2.png) [@ckarpyszyn2](https://devforum.zoom.us/u/ckarpyszyn2)\
**Post date:** [November 17, 2022, 7:02pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/32 "2022-11-17T19:02:25Z")

</div>

I want to keep this bumped. This is a high priority issue for our company which will impact Zoom users in production. We need an answer ASAP.

---

<div class="post-metadata">

**Author:** ![John\_smith\_1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/john_smith_1/32/38241_2.png) [@John\_smith\_1](https://devforum.zoom.us/u/John_smith_1)\
**Post date:** [November 17, 2022, 7:18pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/33 "2022-11-17T19:18:28Z")

</div>

I guess that no answer is an answer! 😶

---

<div class="post-metadata">

**Author:** ![shariq.torres](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shariq.torres/32/39899_2.png) [@shariq.torres](https://devforum.zoom.us/u/shariq.torres)\
**Post date:** [November 17, 2022, 7:19pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/34 "2022-11-17T19:19:38Z")

</div>

We are looking at some options right now. I thought I would have an answer by now, but the stakeholders are still working through some things. I hope to know more by the end of the day.

---

<div class="post-metadata">

**Author:** ![sadie.dickman](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sadie.dickman/32/43114_2.png) [@sadie.dickman](https://devforum.zoom.us/u/sadie.dickman)\
**Post date:** [November 17, 2022, 8:11pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/35 "2022-11-17T20:11:54Z")

</div>

> [@shariq.torres](#):
>
> There was another email communication that was sent in May of this year as well as an another email in August. There was also the announcement that you linked. I believe around spring time, the documentation was changed to reflect sending access\_tokens via the headers.

When you get a sec, would you mind clarifying what notifications or email list we have to sign up for to be notified of breaking changes like this? This is the second time we’ve been caught off guard by a potentially breaking change because none of my crew has received notifications. Is there an email list we need to sign up for? A particular category or tag we should follow here in Zoom dev? All of the support pages I can find with announcements and change logs mix minor issues in with major, so it’s impossible to understand when something critical like this is coming up.

---

<div class="post-metadata">

**Author:** ![John\_smith\_1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/john_smith_1/32/38241_2.png) [@John\_smith\_1](https://devforum.zoom.us/u/John_smith_1)\
**Post date:** [November 17, 2022, 9:33pm UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/36 "2022-11-17T21:33:42Z")

</div>

@shariq.torres Hi Shariq! i was wondering if you have any updates ???

---

<div class="post-metadata">

**Author:** ![ckarpyszyn2](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ckarpyszyn2/32/40279_2.png) [@ckarpyszyn2](https://devforum.zoom.us/u/ckarpyszyn2)\
**Post date:** [November 18, 2022, 12:05am UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/37 "2022-11-18T00:05:54Z")

</div>

I need an update to this today to be able to make a business decision that won’t disrupt paying Zoom users.

---

<div class="post-metadata">

**Author:** ![shariq.torres](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shariq.torres/32/39899_2.png) [@shariq.torres](https://devforum.zoom.us/u/shariq.torres)\
**Post date:** [November 18, 2022, 1:55am UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/38 "2022-11-18T01:55:39Z")

</div>

We are going to delay enforcing this until Feb 2023. We apologize for the late communications on this.

---

<div class="post-metadata">

**Author:** ![ckarpyszyn2](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ckarpyszyn2/32/40279_2.png) [@ckarpyszyn2](https://devforum.zoom.us/u/ckarpyszyn2)\
**Post date:** [November 18, 2022, 3:31am UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/39 "2022-11-18T03:31:42Z")

</div>

Thank you @shariq.torres for the help there.

---

<div class="post-metadata">

**Author:** ![rich](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rich/32/1029_2.png) [@rich](https://devforum.zoom.us/u/rich)\
**Post date:** [November 18, 2022, 8:49am UTC](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/40 "2022-11-18T08:49:24Z")

</div>

hi Shariq

so no update tomorrow ? As others have said, is there an email service or forum we can follow to get more advanced notice of major changes ?

[Previous page](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782.md?page=1)

[Next page](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782.md?page=3)
