DOUBLE encode meeting UUIDs?

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 --> 500

So I figured that was the problem. But when I URL-encode it, I got a 404 on the call:

GET --> 404

It wasn’t until I DOUBLE-encoded the UUID that I got a result… What gives?


Hey @ryan3,

This is the expected flow as of now. You must double url encode the uuid if it includes a slash.

We are working to fix this in a future release.