# Bug in cloud recording API call "Retrieve a meeting's all recordings"

**URL:** <https://devforum.zoom.us/t/bug-in-cloud-recording-api-call-retrieve-a-meetings-all-recordings/1101>\
**Category:** API and Webhooks\
**Created:** [March 19, 2018, 2:45pm UTC](https://devforum.zoom.us/t/bug-in-cloud-recording-api-call-retrieve-a-meetings-all-recordings/1101 "2018-03-19T14:45:19Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Natalie\_Matthews1](https://avatars.discourse-cdn.com/v4/letter/n/76d3ee/32.png) [@Natalie\_Matthews1](https://devforum.zoom.us/u/Natalie_Matthews1)\
**Post date:** [March 19, 2018, 2:45pm UTC](https://devforum.zoom.us/t/bug-in-cloud-recording-api-call-retrieve-a-meetings-all-recordings/1101/1 "2018-03-19T14:45:19Z")

</div>

This API call:

[https://zoom.github.io/api/#retrieve-a-meeting-s-all-recordings](https://zoom.github.io/api/#retrieve-a-meeting-s-all-recordings)

&nbsp;

There is 1 required path argument:

“meetingId - The meeting ID or meeting UUID. If given meeting ID, will take the last meeting instance.”

&nbsp;

The call is made in this format:

GET [https://api.zoom.us/v2/meetings/](https://api.zoom.us/v2/meetings/){meetingId}/recordings

&nbsp;

The problem is that the UUID can include the “/” character. If there is a case where there are one or more “/” at the beginning or the end of a UUID then then those “/” are viewed as duplicates of the “/” that is the delimiter and are deleted when the call is made. When Zoom receives the request, since the “/” has been removed from the UUID, Zoom returns a 404 because it no longer recognizes the UUID.

I have also tried URL encoding the UUID but this will not work because the Zoom API is not expecting a URL encoded version of the UUID and I receive the response “400 Bad Request”.

This is serious because this makes it impossible to get the recording information for a meeting whose UUID begins or ends with a slash.

The UUID needs to be encoded in a URL safe format or the API needs to accept a URL encoded version of the UUID.

---

<div class="post-metadata">

**Author:** ![Zoom\_Developer](https://avatars.discourse-cdn.com/v4/letter/z/eb8c5e/32.png) [@Zoom\_Developer](https://devforum.zoom.us/u/Zoom_Developer)\
**Post date:** [March 19, 2018, 6:18pm UTC](https://devforum.zoom.us/t/bug-in-cloud-recording-api-call-retrieve-a-meetings-all-recordings/1101/2 "2018-03-19T18:18:01Z")

</div>

Natalie, thanks for reporting this and this definitely looks like a bug on our side. we will revert back shortly.

---

<div class="post-metadata">

**Author:** ![Natalie\_Matthews1](https://avatars.discourse-cdn.com/v4/letter/n/76d3ee/32.png) [@Natalie\_Matthews1](https://devforum.zoom.us/u/Natalie_Matthews1)\
**Post date:** [March 21, 2018, 6:41pm UTC](https://devforum.zoom.us/t/bug-in-cloud-recording-api-call-retrieve-a-meetings-all-recordings/1101/3 "2018-03-21T18:41:04Z")

</div>

Thanks! Please let us know when it is fixed.

This also affects other calls in the “Cloud Recording” category as well as calls in the “Dashboards” and “Reports” categories.

---

<div class="post-metadata">

**Author:** ![harris\_yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/harris_yang/32/155_2.png) [@harris\_yang](https://devforum.zoom.us/u/harris_yang)\
**Post date:** [March 23, 2018, 1:46am UTC](https://devforum.zoom.us/t/bug-in-cloud-recording-api-call-retrieve-a-meetings-all-recordings/1101/4 "2018-03-23T01:46:05Z")

</div>

@Natalie, please test with **no** encode meeting UUIDs.&nbsp;

---

<div class="post-metadata">

**Author:** ![Dean\_Si](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dean_si/32/764_2.png) [@Dean\_Si](https://devforum.zoom.us/u/Dean_Si)\
**Post date:** [March 23, 2018, 2:41am UTC](https://devforum.zoom.us/t/bug-in-cloud-recording-api-call-retrieve-a-meetings-all-recordings/1101/5 "2018-03-23T02:41:10Z")

</div>

Hi Natalie

We have discussed encoding the UUID to avoid “/”, but this way is not friendly to the developer to use REST API, they should encoding the UUID twice because the browser will&nbsp;automatically decode the path once.

So in this case, we pass the UUID&nbsp;and obtain UUID based on regular expression interception path, the developer should do nothing and keep UUID not encoded.

Please test again with no encoded meeting UUID

---

<div class="post-metadata">

**Author:** ![Natalie\_Matthews1](https://avatars.discourse-cdn.com/v4/letter/n/76d3ee/32.png) [@Natalie\_Matthews1](https://devforum.zoom.us/u/Natalie_Matthews1)\
**Post date:** [March 23, 2018, 1:02pm UTC](https://devforum.zoom.us/t/bug-in-cloud-recording-api-call-retrieve-a-meetings-all-recordings/1101/6 "2018-03-23T13:02:12Z")

</div>

Hi Dean,

I don’t understand what you are asking me to try again. Any call with the the uuid in the path will fail if there is a “/” at the beginning or end of the uuid. If there hasn’t been a fix then this issue hasn’t changed.

Is it possible to change how uuids are generated so that they don’t include that character?

---

<div class="post-metadata">

**Author:** ![Deannnnnnnnn\_Si](https://avatars.discourse-cdn.com/v4/letter/d/c0e974/32.png) [@Deannnnnnnnn\_Si](https://devforum.zoom.us/u/Deannnnnnnnn_Si)\
**Post date:** [March 26, 2018, 1:35am UTC](https://devforum.zoom.us/t/bug-in-cloud-recording-api-call-retrieve-a-meetings-all-recordings/1101/7 "2018-03-26T01:35:26Z")

</div>

Hi Natalie

I mean that&nbsp;if there is a “/” at the beginning or end of the uuid, the call with the&nbsp;uuid in the path will&nbsp;be OK, and I have&nbsp;successfully tested with UUID such as “/Qac9eD8NSPOjZJ4DPGo5Zg==/”, so I want you to test again.

If it still fails, please provide your more detail of using process

---

<div class="post-metadata">

**Author:** ![Natalie\_Matthews1](https://avatars.discourse-cdn.com/v4/letter/n/76d3ee/32.png) [@Natalie\_Matthews1](https://devforum.zoom.us/u/Natalie_Matthews1)\
**Post date:** [March 26, 2018, 3:35pm UTC](https://devforum.zoom.us/t/bug-in-cloud-recording-api-call-retrieve-a-meetings-all-recordings/1101/8 "2018-03-26T15:35:09Z")

</div>

Okay. I just tried again with two sample UUIDs that begin with “/”. I have confirmed in our account that the videos with these ids still exist and were not deleted but we receive a 404 when calling the retrieve meetings recordings call for both of these.

I am using the python requests module. I set allow\_redirects to False and then for both UUIDs I receive a 301 and a redirect to the URL with the “extra” “/” deleted.

Can you explain the method that you were using and why it may be different?

---

<div class="post-metadata">

**Author:** ![Natalie\_Matthews1](https://avatars.discourse-cdn.com/v4/letter/n/76d3ee/32.png) [@Natalie\_Matthews1](https://devforum.zoom.us/u/Natalie_Matthews1)\
**Post date:** [March 28, 2018, 2:40pm UTC](https://devforum.zoom.us/t/bug-in-cloud-recording-api-call-retrieve-a-meetings-all-recordings/1101/9 "2018-03-28T14:40:22Z")

</div>

Alright!

I’ve done more testing and I’ve gotten to the bottom of this issue.

We are using a function called urljoin from the python urllib module. This function will remove the extra forward slash character.&nbsp;So, in case anyone has the same issue, you need to use pure string concatenation to put the request url together.

---

<div class="post-metadata">

**Author:** ![alex.unger](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/alex.unger/32/150_2.png) [@alex.unger](https://devforum.zoom.us/u/alex.unger)\
**Post date:** [December 19, 2018, 12:28am UTC](https://devforum.zoom.us/t/bug-in-cloud-recording-api-call-retrieve-a-meetings-all-recordings/1101/10 "2018-12-19T00:28:40Z")

</div>

Natalie,

I had the same issue but it is solved now that I am using Meeting ID rather than Meeting UUID for the api calls.

-Alex

---

<div class="post-metadata">

**Author:** ![Shavon\_Golbourne](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shavon_golbourne/32/18248_2.png) [@Shavon\_Golbourne](https://devforum.zoom.us/u/Shavon_Golbourne)\
**Post date:** [November 4, 2020, 9:44pm UTC](https://devforum.zoom.us/t/bug-in-cloud-recording-api-call-retrieve-a-meetings-all-recordings/1101/11 "2020-11-04T21:44:04Z")

</div>

Try ensuring that no authorization header is sent with the request. I am using axios to make the request and the authorization header is set to ‘Authorization’:’’

get\_request= download\_url  
config={  
headers:{  
‘Acceept-Encoding’:‘gzip, deflate,br’,  
‘Accept’:`_/_’,  
‘Connection’:‘keep-alive’,  
‘Authorization’:’’  
},  
params:{  
access\_token: token  
}  
}  
Hopefully this helps.

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [November 5, 2020, 6:14pm UTC](https://devforum.zoom.us/t/bug-in-cloud-recording-api-call-retrieve-a-meetings-all-recordings/1101/12 "2020-11-05T18:14:51Z")

</div>

Thanks for sharing, @Shavon_Golbourne! 🙂
