# Recording URL downloads returning 403?

**URL:** <https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576>\
**Category:** API and Webhooks\
**Created:** [August 19, 2019, 6:27pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576 "2019-08-19T18:27:09Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![clippermadness](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/clippermadness/32/1039_2.png) [@clippermadness](https://devforum.zoom.us/u/clippermadness)\
**Post date:** [August 19, 2019, 6:27pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/1 "2019-08-19T18:27:10Z")

</div>

Our application is receiving 403 errors when attempting to download video recordings. Our code was working as recently as Friday. Has something changed?

---

<div class="post-metadata">

**Author:** ![clippermadness](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/clippermadness/32/1039_2.png) [@clippermadness](https://devforum.zoom.us/u/clippermadness)\
**Post date:** [August 19, 2019, 6:40pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/2 "2019-08-19T18:40:02Z")

</div>

If I use the download\_url provided in the recordings API response in a browser, the download works fine. But our programmatic downloads fail. This implies that some header is required that was not required before.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [August 19, 2019, 8:25pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/4 "2019-08-19T20:25:07Z")

</div>

Hey @clippermadness,

Thanks for posting, we are escalating to our eng team and will be back with a response asap.

Possible work around in the meantime:

> [@Unable to get Recording URL's filename and extension using Python](https://devforum.zoom.us/t/unable-to-get-recording-urls-filename-and-extension-using-python/5558/12):
>
> Ok, that should have tipped it off! It’s cookies! The initial request returns a 302 and sets some cookies in the response. You must use those cookies when following the redirect.

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![proveedores](https://avatars.discourse-cdn.com/v4/letter/p/48db29/32.png) [@proveedores](https://devforum.zoom.us/u/proveedores)\
**Post date:** [August 19, 2019, 9:24pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/5 "2019-08-19T21:24:09Z")

</div>

Tengo el mismo problema

* * *

I have the same problem

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [August 19, 2019, 9:30pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/6 "2019-08-19T21:30:09Z")

</div>

Thanks @proveedores, we will provide an update as soon as we can.

* * *

Proporcionaremos una actualización tan pronto como podamos.

-Tommy

---

<div class="post-metadata">

**Author:** ![proveedores](https://avatars.discourse-cdn.com/v4/letter/p/48db29/32.png) [@proveedores](https://devforum.zoom.us/u/proveedores)\
**Post date:** [August 19, 2019, 11:34pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/8 "2019-08-19T23:34:11Z")

</div>

@tommy qué solución podríamos aplicar mientras tanto?

---

<div class="post-metadata">

**Author:** ![James\_Hale](https://avatars.discourse-cdn.com/v4/letter/j/ebca7d/32.png) [@James\_Hale](https://devforum.zoom.us/u/James_Hale)\
**Post date:** [August 20, 2019, 12:02am UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/9 "2019-08-20T00:02:01Z")

</div>

We’re affected too.

It’s damn embarrassing how often part of my app breaks because Zoom changes the API or something that the API provides/depends upon.

Thanks @clippermadness for posting, so I can now stop debugging my own code and instead implement a workaround.

Requiring a cookie is a pretty cooked security solution - even CURL is busted. No error message provided in the body either.

---

<div class="post-metadata">

**Author:** ![clippermadness](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/clippermadness/32/1039_2.png) [@clippermadness](https://devforum.zoom.us/u/clippermadness)\
**Post date:** [August 20, 2019, 4:13am UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/10 "2019-08-20T04:13:11Z")

</div>

Workaround if you’re using golang FWIW:

> <https://stackoverflow.com/questions/18414212/golang-how-to-follow-location-with-cookie>

---

<div class="post-metadata">

**Author:** ![shaharsol](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shaharsol/32/1601_2.png) [@shaharsol](https://devforum.zoom.us/u/shaharsol)\
**Post date:** [August 20, 2019, 9:23am UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/11 "2019-08-20T09:23:22Z")

</div>

Does anyone have a quick solution for nodejs? preferably using the request npm module?

---

<div class="post-metadata">

**Author:** ![shaharsol](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shaharsol/32/1601_2.png) [@shaharsol](https://devforum.zoom.us/u/shaharsol)\
**Post date:** [August 20, 2019, 9:37am UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/12 "2019-08-20T09:37:32Z")

</div>

@tommy this is ridiculous that you make those changes and break our apps. simply ridiculous. I have angry users to answer to and they dont care that Zoom broke the API, they don’t even know what API is, they just want their recordings. Please, this needs to be fixed ASAP, please revert back to the old method.

---

<div class="post-metadata">

**Author:** ![proveedores](https://avatars.discourse-cdn.com/v4/letter/p/48db29/32.png) [@proveedores](https://devforum.zoom.us/u/proveedores)\
**Post date:** [August 20, 2019, 2:43pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/13 "2019-08-20T14:43:01Z")

</div>

@tommy no se publicaron actualizaciones como estas como para preparar nuestras aplicaciones para estos cambios, realmente es fastidioso.

---

<div class="post-metadata">

**Author:** ![Emanuel\_Aguirre](https://avatars.discourse-cdn.com/v4/letter/e/898d66/32.png) [@Emanuel\_Aguirre](https://devforum.zoom.us/u/Emanuel_Aguirre)\
**Post date:** [August 20, 2019, 3:13pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/14 "2019-08-20T15:13:55Z")

</div>

they always do this, it was the same with v1 … you will notice API changes when your code start failing … ugh 😡

---

<div class="post-metadata">

**Author:** ![selva.iyyamperumal](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/selva.iyyamperumal/32/50293_2.png) [@selva.iyyamperumal](https://devforum.zoom.us/u/selva.iyyamperumal)\
**Post date:** [August 20, 2019, 5:49pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/15 "2019-08-20T17:49:39Z")

</div>

We got affected too. When it will be fixed and what will happen to the recordings? Lots of questions from our customer. How can we upload those recordings to customers (to their Google Drive or YouTube etc) Thanks.

---

<div class="post-metadata">

**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\
**Post date:** [August 20, 2019, 6:01pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/16 "2019-08-20T18:01:40Z")

</div>

Hi @selva.iyyamperumal @Emanuel_Aguirre @proveedores @clippermadness @James_Hale

For updates, please refer to our this forum post - [Update: Recording download url 403 error](https://devforum.zoom.us/t/update-recording-download-url-403-error/5608). We’re working on resolving the issue asap.

---

<div class="post-metadata">

**Author:** ![selva.iyyamperumal](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/selva.iyyamperumal/32/50293_2.png) [@selva.iyyamperumal](https://devforum.zoom.us/u/selva.iyyamperumal)\
**Post date:** [August 21, 2019, 2:04am UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/17 "2019-08-21T02:04:56Z")

</div>

Please give an estimate. What we have to tell our customers?

---

<div class="post-metadata">

**Author:** ![James\_Hale](https://avatars.discourse-cdn.com/v4/letter/j/ebca7d/32.png) [@James\_Hale](https://devforum.zoom.us/u/James_Hale)\
**Post date:** [August 21, 2019, 4:39am UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/18 "2019-08-21T04:39:02Z")

</div>

This isn’t perfect but it should be a good start. Key for the request module is that followRedirect setting.

```
function getZoomVideo (url) {
  return new Promise((resolve, reject) => {
    request(url, { followRedirect: false }, function (err, res, body) {
      if (err) {
        reject(err);
      } else {
        if (res.statusCode === 302) {
          let cookie = '';
          if (res.headers['set-cookie']) cookie = res.headers['set-cookie'].map(c=>c.substr(0, c.indexOf(";"))).reduce((a, b) => a + "; " + b);

          request(url, {
            followRedirect: true,
            headers: {
              'Cookie': cookie,
            }
          }, function (err, res, body) {
            if (err) {
              reject(err)
            } else {
              resolve(res)
            }
          });
        } else {
          resolve(res);
        }
      }
    })
  })
}

(async () => {
  const videoFile = await getZoomVideo('[zoom video url]');

  console.log(videoFile.statusCode);
  console.log(videoFile.headers['content-length']);
})();
```

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [August 21, 2019, 3:33pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/19 "2019-08-21T15:33:18Z")

</div>

@James_Hale, @selva.iyyamperumal, @Emanuel_Aguirre, @proveedores, @shaharsol, @clippermadness,

Thanks for your patience, the issue is now fixed.

> [@Update: Recording download url 403 error](https://devforum.zoom.us/t/update-recording-download-url-403-error/5608/10):
>
> Hi @Everyone, Good news! Our Engineers have worked tirelessly overnight to resolve the download url issue which you are experiencing. Now that the fix is in place, please try to use your access token with the download url to confirm that it is working. Let us know if you are still experiencing this or any other issues. Thanks

-Tommy

---

<div class="post-metadata">

**Author:** ![drosentrater](https://avatars.discourse-cdn.com/v4/letter/d/e0b2c6/32.png) [@drosentrater](https://devforum.zoom.us/u/drosentrater)\
**Post date:** [August 21, 2019, 6:08pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/21 "2019-08-21T18:08:27Z")

</div>

It’s working for me! Thank you!

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [August 21, 2019, 6:18pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/22 "2019-08-21T18:18:59Z")

</div>

Happy to hear!

-Tommy

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 6:39pm UTC](https://devforum.zoom.us/t/recording-url-downloads-returning-403/5576/23 "2020-08-21T18:39:33Z")

</div>

Closed on August 21, 2020, 6:39pm UTC


