But always returns the “User does not exist” message. It would be great to get some clarity as to what I’m doing wrong. Do I need to add the user to my account first? That doesn’t seem to make (human) logical sense if so - these are hundreds of random people who are attending an event and I wouldn’t think should have any connection to my own account. Many (most?) of them will already have their own Zoom account, and some won’t.
What I’m trying to mimic with the API is looking up the meeting on the web portal, going to the Registration URL and filling this form out once for every single attendee, which as far as I can see is very much the manual approach to what I feel I am trying to automate - albeit perhaps wrongly - via the API.
Thanks in advance for any help - one thing all my searching on this forum has at least made clear is that you guys are really helpful and responsive.
After diving into tons of support threads I found a couple that alluded to needing to turn off authentication profiles - this one (though related to a different error) and this one (which I think is inaccurate as I was getting “user does not exist” for an email address that IS a Zoom account) in particular.
Anyway, I’ve now managed to get this working by adding
"meeting_authentication" => false
to the API call that creates the meeting, i.e. disabling “Only authenticated users can join”.
Is this correct? It seems quite illogical that in order to turn on registration you have to turn off authentication.
This suggests that if you use registration to pre-authorise meeting participants then registering someone without a Zoom account means they can join the meeting without an account. If so, that’s fine - just want to get this straight in my mind and make sure I’m doing the right thing and not compromising meeting security in any way.
If you want to register participants by their email address, just make sure you aren’t using any other authentication profiles (e.g. participants must have a Zoom account or participants’ email addresses must be in the allowlist of specified domains) as these can mess with registration.
If you’re doing registration properly, you shouldn’t need any authentication profiles as the registration will be more precise than those authentication profiles can be.
This whole thing opened up a huge can of worms for us where we ended up discovering many more limitations to trying to have registered meetings on Zoom, but this is probably no longer the place for those issues.
Thanks for your response. We are now being forced to work with allowing users without a zoom account to register. In our previous process, the salespeople (who manually filled the registration form for our users) used the zoom account as an extra certainty that the email was valid. But now, we can’t depend on this while we’re trying to automate the process.
But I guess I have to accept that that’s what the Zoom API is, for now If it does change, please let us know!