# DOUBLE encode meeting UUIDs? **URL:** \ **Category:** API and Webhooks\ **Created:** [July 9, 2020, 10:41pm UTC](https://devforum.zoom.us/t/double-encode-meeting-uuids/23729 "2020-07-09T22:41:33Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![ryan3](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ryan3/32/4260_2.png) [@ryan3](https://devforum.zoom.us/u/ryan3)\ **Post date:** [July 9, 2020, 10:41pm UTC](https://devforum.zoom.us/t/double-encode-meeting-uuids/23729/1 "2020-07-09T22:41:33Z")
Trying to get the recordings of a meeting, using the `/meetings/{meetingId}/recordings` API. All works fine usually. Today we got a meeting with a UUID of `/nk84I4+SbONSeE5ScfjUQ==`. The request failed because I wasn’t URL-encoding that value: `GET https://api.zoom.us/v2/meetings//nk84I4+SbONSeE5ScfjUQ==/recordings` --\> 500 So I figured that was the problem. But when I URL-encode it, I got a 404 on the call: `GET https://api.zoom.us/v2/meetings/%2Fnk84I4%2BSbONSeE5ScfjUQ%3D%3D/recordings` --\> 404 It wasn’t until I DOUBLE-encoded the UUID that I got a result… What gives? `GET https://api.zoom.us/v2/meetings/%252Fnk84I4%252BSbONSeE5ScfjUQ%253D%253D/recordings` ---
**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:** [July 14, 2020, 8:55pm UTC](https://devforum.zoom.us/t/double-encode-meeting-uuids/23729/2 "2020-07-14T20:55:22Z")
Hey @ryan3, This is the expected flow as of now. You must double [url encode](https://www.urldecoder.org/) the uuid if it includes a slash. We are working to fix this in a future release. Thanks, Tommy ---
**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, 10:41pm UTC](https://devforum.zoom.us/t/double-encode-meeting-uuids/23729/3 "2020-08-21T22:41:42Z")