# Access token invalided

**URL:** <https://devforum.zoom.us/t/access-token-invalided/83910>\
**Category:** Meetings\
**Created:** [March 1, 2023, 5:09am UTC](https://devforum.zoom.us/t/access-token-invalided/83910 "2023-03-01T05:09:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [March 1, 2023, 8:59pm UTC](https://devforum.zoom.us/t/access-token-invalided/83910/2 "2023-03-01T20:59:49Z")

</div>

Hi @hbetancur  
It looks like you are passing the access token as a query parameter.  
We recently made some security enhancements to the way we manage access tokens, learn more about that here:

> [@\[Security Update\] No token values in URL query parameters](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782/4):
>
> Yes it does. You would need to put the access\_token in the ‘Authorization’ header for the request. In the curl example, you would have to use the output flag, i.e, --output /path/to/download.file.

[https://marketplace.zoom.us/docs/guides/auth/oauth/#step-2-request-access-token](https://marketplace.zoom.us/docs/guides/auth/oauth/#step-2-request-access-token)

Hope this helps,  
Elisa

---

_[View the full topic](https://devforum.zoom.us/t/access-token-invalided/83910)._