# Issues with download a recording

**URL:** <https://devforum.zoom.us/t/issues-with-download-a-recording/134430>\
**Category:** Meetings\
**Created:** [June 25, 2025, 1:54am UTC](https://devforum.zoom.us/t/issues-with-download-a-recording/134430 "2025-06-25T01:54:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ogen.odisho\_zp](https://avatars.discourse-cdn.com/v4/letter/o/958977/32.png) [@ogen.odisho\_zp](https://devforum.zoom.us/u/ogen.odisho_zp)\
**Post date:** [June 25, 2025, 1:54am UTC](https://devforum.zoom.us/t/issues-with-download-a-recording/134430/1 "2025-06-25T01:54:08Z")

</div>

I have a couple of questions.

1. In the recording.completed webhook, is there a way to increase the ttl of the download\_token? The docs say it expires in 24 hours but I’d like to know if it can be set up to expire in a week or something.
2. I recently encountered a scenario where the `download_token` from the `recording.completed` webhook was expired so I used the Zoom user’s oauth access token to request the associated `download_url` from the webhook but I got a 401.  
**This used to work.**  
I even checked the Zoom documentation and it says that Zoom users’ access tokens may be used to download recordings. Has this behaviour changed? (I am aware that another possibility is to query the recording API to get a `download_access_token` and a new `download_url`, but I’m interested in knowing why the behaviour seems to have changed).

---

<div class="post-metadata">

**Author:** ![expertswho](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/expertswho/32/60945_2.png) [@expertswho](https://devforum.zoom.us/u/expertswho)\
**Post date:** [June 25, 2025, 1:44pm UTC](https://devforum.zoom.us/t/issues-with-download-a-recording/134430/2 "2025-06-25T13:44:37Z")

</div>

hi @ogen.odisho_zp ,

You are not going to get tokens extended. Is that not specific to that hook?

When you use OAuth, you get a token that lasts much longer, and you should also take note of the refresh token, which will allow you to get a new token when it expires.  
So for that reason, there is no need to worry when you are programmatically going to access the download.  
Make sure you are using the right token.

All the best

John

---

<div class="post-metadata">

**Author:** ![ogen.odisho\_zp](https://avatars.discourse-cdn.com/v4/letter/o/958977/32.png) [@ogen.odisho\_zp](https://devforum.zoom.us/u/ogen.odisho_zp)\
**Post date:** [August 4, 2025, 1:06am UTC](https://devforum.zoom.us/t/issues-with-download-a-recording/134430/3 "2025-08-04T01:06:37Z")

</div>

Thanks, I’m unmarking this as a solution because I still want my second question to be addressed by Zoom.

---

<div class="post-metadata">

**Author:** ![expertswho](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/expertswho/32/60945_2.png) [@expertswho](https://devforum.zoom.us/u/expertswho)\
**Post date:** [August 4, 2025, 7:43am UTC](https://devforum.zoom.us/t/issues-with-download-a-recording/134430/4 "2025-08-04T07:43:25Z")

</div>

hi @ogen.odisho_zp ,

Follow through this and compare with your code.

> **[Zoom Meeting API querying tips - Download recordings using webhooks](https://developers.zoom.us/blog/meeting-api-querying-tips-part4/)**
>
> Join Developer Advocate Elisa Levet in this blog post series as she takes a deep dive into the world of the Zoom REST API.

all the best

john

---

<div class="post-metadata">

**Author:** ![ogen.odisho\_zp](https://avatars.discourse-cdn.com/v4/letter/o/958977/32.png) [@ogen.odisho\_zp](https://devforum.zoom.us/u/ogen.odisho_zp)\
**Post date:** [August 4, 2025, 8:21am UTC](https://devforum.zoom.us/t/issues-with-download-a-recording/134430/5 "2025-08-04T08:21:56Z")

</div>

> [@ogen.odisho\_zp](#):
>
> Zoom users’ access tokens may be used to download recordings

I understand that will work, but according to the docs here: [Using Zoom APIs](https://developers.zoom.us/docs/api/using-zoom-apis/#download-url) , I shouldn’t need to query the “Get meeting recordings” endpoint at all.

The link says:

> If a user has authorized and installed your OAuth app that contains recording scopes, use the `download_access_token` or the user’s [OAuth access token](https://developers.zoom.us/docs/integrations/oauth/)\* to download the file.

In my case, the user had authorized and installed my OAuth app with the `recording:read` scope, yet the user’s OAuth access token was not authorized to download the file.

---

<div class="post-metadata">

**Author:** ![expertswho](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/expertswho/32/60945_2.png) [@expertswho](https://devforum.zoom.us/u/expertswho)\
**Post date:** [August 4, 2025, 10:37am UTC](https://devforum.zoom.us/t/issues-with-download-a-recording/134430/6 "2025-08-04T10:37:52Z")

</div>

@ogen.odisho_zp ,

Which is explained by Elisa ins the link I have shared

> **[Zoom Meeting API querying tips - Download recordings using webhooks](https://developers.zoom.us/blog/meeting-api-querying-tips-part4/)**
>
> Join Developer Advocate Elisa Levet in this blog post series as she takes a deep dive into the world of the Zoom REST API.

The user must be authorised to download the file within the account.  
Creating API’s does not grant blanket permission to any data unless they are given access IRL.  
So, if this user tried to download the file from the [Zoom.us](http://Zoom.us) site, do they have permission?

I suggest you set this up with the user being the account holder of the meeting recorded.  
They will have access to the recording.  
Giving a meeting scope just gives access to the api, not a guaranteed access to the data.  
So I suggest you check that first.  
all the best

John
