Currently experiencing problems extracting the UUID from the Endpoint because one of the characters in the UUID is “/”. As there are endpoints that could result in a webinar report, I had hoped to collect the UUID with a simple 'FIND webinars/ in the endpoint, then whatever is between that “/” and the next “/” is the UUID.
Perhaps stick to URL-safe characters for ID generation?
I’ve never seen that occur but that would be catastrophic if I had that in my current project. Right now I was thinking of using strings to store those, but if ‘/’ is a valid character then…well I’m not sure what I can use to hold those?
I just got back to testing this, and hopefully the ‘fix’ happened in November; but I’m not really sure what ‘the fix’ is doing. A recent meeting uuid still had the “/” in it. I still get an error when I try to make a GET request to the API to pull a participant report.
I think @michael_p.zoom recommended “double URL encoding” the slash in another post.
So instead of / or a single encoding %2F, you would send the double-encoded slash as %252F. I would experiment with it to make sure it works for your setup.
Following up, @Jonathan_Champ is correct, you should be able to double URL encode the UUID to get it to work. So instead of /YPJDeEgmRFOA/EslXIsaoA== your UUID would be %252FYPJDeEgmRFOA%252FEslXIsaoA%253D%253D.
That’s what I did - in the screenshot in my post I had replaced the ‘/’ with that string but then it returned the ‘meeting id is invalid or not end’. I’ve tried that with a few UUID’s and it always returns the meeting id is invalid response.
The webinar has ended definitely. I need to do the webinar UUID, because otherwise I only get the most recent attendees and this is a re-occurring webinar so I need to get all the webinars, so that’s why I’m using UUID because it’s a unique identifier.
It works to pass through the WebinarUUID when it doesn’t had a ‘/’ in the ID. So it does work to use the UUID to get the results.