Hello Zoom support community,
I know things have changed a bit since with the some policies within the Zoom API and I apologize in advance if I bring up an issue already mentioned elsewhere.
Description
I am looking for advice on the best way to handle the following issue. The below examples have been striped of details to avoid data breaches.
I have had a API in place for a few months now which collects all the meetings from the previous day(s) then it gets the HOST_uuid via GET /report/meetings/{meetingId} (link).
Related to data loss that occurred on March 13th, I started to record errors. I have collected several UUIDās of hosts that receive the below error. I confirmed that these HOST_UUID did exist in our system previously and there are a couple different cases detailed here:
-
- User is part of our organization and has multiple UUIDās assigned and all were deactivated on 3/14/2020.
- No active account within Zoom but is still part of our organization.
-
- Users are part of the organization but has two organizational emails.
- One Zoom account
- the hosted meeting was using the email not associated with the Zoom account.
-
- Users with 2 active Zoom accounts
- one account has the organization email the other has an alias of the organization email with a āeā prefix.
-
- Users who were part of our organization but have moved on.
- This specific case has one meeting using our organizational account, but the error still displays.
- The other meeting is with their external organization email and the failure is expected.
What is the best way to report and get support on these? Is it secure to post the UUIDs here?
Error
{
ācodeā: 1001,
āmessageā: āUser xxxxxxxxxxxxxxx not exist or not belong to this account.ā
}
Which App Type (OAuth / Chatbot / JWT / Webhook)?
- Using JWT
- example call - GET https://api.zoom.us/v2/report/meetings/0sC9L8TWRNGvnSg+smi52g==
Which Endpoint/s?
Knowing the API endpoint/s can help us to identify your issue faster. Please link the ones you need help/have a question with.
How To Reproduce (If applicable)
Steps to reproduce the behavior:
Additional context
Add any other context about the problem here.