No, I didn’t try double-encoding the meeting UUID. I’ll try that.
This worked. I’m now double hex encoding the meeting ID. And, I can now successfully retrieve participants for this uuid: /JcknqNDQo6A/BnHsjsYUg==
We’re glad that it worked for you, we’ve also updated our API documentation to reflect our suggestion of double encoding the UUID .
Let us know if you need anything else.
Hi @Michael_Purnell I’m having the same issue and have tried double encoding as you’ve suggested but I’m still not able to retrieve any past meeting data. Every uuid I try results in the 3001 error.
To check myself I’ve tried encoding the uuid shared above (/OterjLTR3eIKqrkEP3j2A==) to see if I’m getting the same result out as you, and I am except the last two D’s in my result are lower case (%252fOterjLTR3eIKqrkEP3j2A%253d%253d). Could that be what’s messing me up? Also if that value is wrong, is there a supported method for doing the hex encoding? Because clearly what I’ve figured out is not working.
Hi. This is high priority. We just went to production with our code. Note that we ARE double hex encoding the uuids in the request to get meeting participants. The problematic meeting uuid is now B634woWXRu+IczdjDrtJ6w==\
The double-encoded uuid is B634woWXRu%252BIczdjDrtJ6w%253D%253D%255C
See this particular message in your log:
“Set-Cookie: cred=A8B5DA7DBE2158F727A61B7662FC5A03; Path=/; Secure; HttpOnly”
“date_time”: “2019-05-24 13:47:10”,
“message”: “This meeting’s details info is not available or ID is not valid.”
“user-agent: UnifySquare Zoom Data Extraction Service (1.0)”
I can’t give you the customer information in this post. Please e-mail or call me.
Can you email us the customer’s email along with meeting ID to firstname.lastname@example.org?
Also, we are now getting the same error for meeting UUID sz8BcXChTS2ZfvFIvvUOXQ==
with meeting ID 917910532
We really need a response on this soon, as, although the UUID is double-hex encoded in the meeting participant list request, the original UUID doesn’t even have any special characters in it.
We are consulting with our engineers regarding your issue, and we will communicate you the updates on your email.
Thank you. There are a few meeting UUIDs for which we have gotten this message that do not appear to have any special characters in them.
Can you send these details in the email to our developer support?
Having the same issue with the UUID, I had double encoded it with “UTF-8” and sent a call to the API, but it had returned the error ‘3001’. I already checked the encoded string at convertstring.com and it matches. Trying at the Zoom API Reference Test Request results in the same error.
Can you please send us these details to email@example.com ? We will continue to assist you on that platform
Facing same issue for every UUID while getting past meetings. Also tried with double encoding still getting same issue.
Please provide your request url, query params, and uuids you are using so we can debug.
Following are the url with uuid.
I am guessing this is happening because the meeting has been deleted.
Meetings are not deleted. these are available. I can get all details about these meetings using ‘meetingid’. Only past_meetings API is not working for me.
Also I have tried by creating new meeting still its not working.
Report and Dashboard APIs needs admin scope. We are using only user scope APIs. So we could not use these APIs.
Could you please check is there any other way to get past meetings details?
Our records indicate that the meeting uuid
gErGry50QNKsDG7jaa5z2w== has never been started.
Can you try again, start the meeting, end the meeting, and then send us the UUID of that meeting?
I have started and ended the meeting and sharing the uuid of the same meeting.