# Double Encoded UUID Does Not Recognize Leading "/"

**URL:** <https://devforum.zoom.us/t/double-encoded-uuid-does-not-recognize-leading/133103>\
**Category:** Meetings\
**Tags:** api\
**Created:** [May 22, 2025, 11:23pm UTC](https://devforum.zoom.us/t/double-encoded-uuid-does-not-recognize-leading/133103 "2025-05-22T23:23:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Greg5](https://avatars.discourse-cdn.com/v4/letter/g/8797f3/32.png) [@Greg5](https://devforum.zoom.us/u/Greg5)\
**Post date:** [May 22, 2025, 11:23pm UTC](https://devforum.zoom.us/t/double-encoded-uuid-does-not-recognize-leading/133103/1 "2025-05-22T23:23:56Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**  
Endpoint: Meetings API - pastMeetingDetails

**Description**  
I am attempting to call the past\_meeting endpoint for a meeting instance with uuid (slightly obfuscated) “/zxXQ6P2Tw2NfVPqXXXXXA==”

Given it starts with a leading “/”, I am double URL-encoding it.

When I attempt to call the URL (with the correct authorization header):  
/v2/past\_meetings/%2FzxXQ6P2Tw2NfVPqXXXXXA%3D%3D%2FzxXQ6P2Tw2NfVPqXXXXXA%3D%3D

I receive back an error response:  
{  
“code”: 3001,  
“message”: “Meeting does not exist: zxXQ6P2Tw2NfVPqXXXXXA==/zxXQ6P2Tw2NfVPqXXXXXA==.”  
}

This response seems to drop the leading “/” in the double encoded uuid. I cannot find a reason why my URL would not work. Is this an error with your API? Or am I missing something?

**Error**  
{  
“code”: 3001,  
“message”: “Meeting does not exist: zxXQ6P2Tw2NfVPqXXXXXA==/zxXQ6P2Tw2NfVPqXXXXXA==.”  
}

**How To Reproduce**  
Call the API with a double-encoded uuid for a uuid with a leading “/”

---

<div class="post-metadata">

**Author:** ![Greg5](https://avatars.discourse-cdn.com/v4/letter/g/8797f3/32.png) [@Greg5](https://devforum.zoom.us/u/Greg5)\
**Post date:** [May 27, 2025, 1:53pm UTC](https://devforum.zoom.us/t/double-encoded-uuid-does-not-recognize-leading/133103/2 "2025-05-27T13:53:35Z")

</div>

Oh, never mind. I followed a bad forum topic when working on this the first time. Double encoding means the more obvious encode the uuid, then encode the result. It does NOT mean to encode the uuid and paste it again. Solved.

---

<div class="post-metadata">

**Author:** ![Iska](https://avatars.discourse-cdn.com/v4/letter/i/53a042/32.png) [@Iska](https://devforum.zoom.us/u/Iska)\
**Post date:** [June 9, 2025, 2:30pm UTC](https://devforum.zoom.us/t/double-encoded-uuid-does-not-recognize-leading/133103/3 "2025-06-09T14:30:47Z")

</div>

I encountered the same problem, but I didn’t understand the solution. I would appreciate further explanation, please.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [June 9, 2025, 2:32pm UTC](https://devforum.zoom.us/t/double-encoded-uuid-does-not-recognize-leading/133103/4 "2025-06-09T14:32:03Z")

</div>

Hi @Iska  
This topic has been closed, can you please create e new thread and include details of the isuse you are facing so we can support you