# Meeting UUID not working in API

**URL:** <https://devforum.zoom.us/t/meeting-uuid-not-working-in-api/64889>\
**Category:** Meetings\
**Created:** [February 25, 2022, 3:01pm UTC](https://devforum.zoom.us/t/meeting-uuid-not-working-in-api/64889 "2022-02-25T15:01:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![PERRONE](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/perrone/32/35036_2.png) [@PERRONE](https://devforum.zoom.us/u/PERRONE)\
**Post date:** [February 25, 2022, 3:01pm UTC](https://devforum.zoom.us/t/meeting-uuid-not-working-in-api/64889/1 "2022-02-25T15:01:31Z")

</div>

Hi,  
with an API call at the endpoint [https://api.zoom.us/v2/report/meetings/{MeetingID}](https://api.zoom.us/v2/report/meetings/%7BMeetingID%7D) i got a meetingUUID startingwith / (ex. /abcdefghijklmnopqrstu==).  
When I try to call [https://api.zoom.us/v2/past\_meetings/{MeetingUUID}](https://api.zoom.us/v2/past_meetings/%7BMeetingUUID%7D) passing the UUID i got from zoomAPI the response says the meeting doesn’t exist but the meeting UUID in the message isn’t correct: it missed the /  
ex.  
{  
“code”: 3001,  
“message”: “Meeting does not exist: abcdefghijklmnopqrstu==.”  
}

I tried to encode the URL but it didn’t works.

Thanks

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [April 23, 2022, 6:51am UTC](https://devforum.zoom.us/t/meeting-uuid-not-working-in-api/64889/2 "2022-04-23T06:51:59Z")

</div>

Hi, @PERRONE,

Thank you for posting! Have you verified that the UUID is correct? Also, can you share how many users attended the meeting?

---

<div class="post-metadata">

**Author:** ![PERRONE](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/perrone/32/35036_2.png) [@PERRONE](https://devforum.zoom.us/u/PERRONE)\
**Post date:** [April 26, 2022, 9:02am UTC](https://devforum.zoom.us/t/meeting-uuid-not-working-in-api/64889/3 "2022-04-26T09:02:36Z")

</div>

Hi [**donte.S**](https://devforum.zoom.us/u/donte.s),

we received this solution to the problem from the zoom support:

However, we point out that endpoints that require UUID return errors if UUID starts with / or containing //

- as for the meeting ID with begins with a / character or contains a // character, you must double-encode the meeting UUID when using the meeting UUID for other API calls.

- sample: /a7dqAr/RwWRrw+6Dl2Ubw==

- double encoded value: %252Fa7dqAr%252FRwWRrw%252B6Dl2Ubw%253D%253D

Thanks.

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [April 26, 2022, 10:13am UTC](https://devforum.zoom.us/t/meeting-uuid-not-working-in-api/64889/4 "2022-04-26T10:13:15Z")

</div>

Thanks for the update and we appreciate you sharing the solution @PERRONE! As mentioned, meeting UUID that begins with a `/` character or contains the `//` characters, you **must** double-encode the meeting UUID before making an API request.

## Source: [Get meeting detail reports](https://marketplace.zoom.us/docs/api-reference/zoom-api/methods#operation/reportMeetingDetails)

 ![Screen Shot 2022-04-26 at 6.02.39 AM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/b/6/b66cf4912ad63bf76a31b9231de452e53ce38c6a.png)