Hi
Below is the information I see for one of the path parameters UUID
" If you provide a meeting UUID that begins with a /
character or contains the //
characters, you must double-encode the meeting UUID before making an API request."
Question: Can all the meeting UUIDs which don’t begin with ‘/’ character or contains the ‘//’ characters also be double encoded before making the API request? or is it very specific that we need to check the UUID that begins a /
character or contains the //
characters and then double-encode the UUID before making the API request.
Thank you for your support!
Thanks
Shasidhar