# ZoomPhone Call Recording Fetching issue

**URL:** <https://devforum.zoom.us/t/zoomphone-call-recording-fetching-issue/89607>\
**Category:** Phone\
**Created:** [June 5, 2023, 6:50am UTC](https://devforum.zoom.us/t/zoomphone-call-recording-fetching-issue/89607 "2023-06-05T06:50:13Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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:** [September 5, 2023, 3:00pm UTC](https://devforum.zoom.us/t/zoomphone-call-recording-fetching-issue/89607/7 "2023-09-05T15:00:35Z")

</div>

Hi @phonebridge-integ  
Thanks for reaching out to us  
We recently made some changes to the way we handle access\_tokens and those should not be passed down as a query parameter anymore

> [@\[Security Update\] No token values in URL query parameters](https://devforum.zoom.us/t/security-update-no-token-values-in-url-query-parameters/78782):
>
> As a part of our continuing efforts to improve the security of Zoom OAuth App Types using Authorization flow, we are removing the ability to set the access tokens, refresh tokens and revoke tokens in the URL query parameters. This change will take effect on February 2023. It is strongly recommended that you update your API calls to set the token values in the Authorization header and not the HTTP query parameters. Failure to do so will result in rejected API calls and a reduced functionality for…

In your request, try to pass this value in your authorization headers, as Bearer token

---

_[View the full topic](https://devforum.zoom.us/t/zoomphone-call-recording-fetching-issue/89607)._
