If a user is created on our corporate account using the API with the “custCreate” action on the /users endpoint, Zoom gets confused as to which user the meeting belongs to.
You cannot start the meeting xxxxxxxxx* because it is hosted by another user
Which App Type (OAuth / Chatbot / JWT / Webhook)?
How To Reproduce (If applicable)
Steps to reproduce the behavior:
- Create new Zoom user outside of the API or the corporate account (simulating someone who already has a personal Zoom account). firstname.lastname@example.org
- Log into Zoom with this basic user. No issues, everything is fine. Works like any basic user.
- Use API to create user using /user endpoint with action: “custCreate” and same email in the user_info section email@example.com. That new user is now associated with our corporate account.
- Use API to create meeting with the user UUID (or email address, doesn’t matter) from step 3.
- Obtain start_url from response in step 4.
- Try to start meeting while logged in as user in step 1.
Message indicating meeting is hosted by another user.
If this is the expected behavior, then it is imperative that any new user created using custCreate under our corporate account can NOT have the exact same email as a possibly existing Zoom user.
We are trying to create meetings for our users regardless of whether they have Zoom accounts but do not want to affect any user that might have an existing personal Zoom account.
From the behavior above, it appears the email address string is unique across all Zoom users and corporate accounts. Need verification.