Description
I’m developing an app from which a user (authenticated via OAuth) can join a meeting (not webinar ATM), but not start it. As long as the meeting not require registration, all is fine as long as the role=0 (with role=1, the join fails silently and the meeting status changes from 1 to 3). I can live with role=0 (and assign cohost permission manually), but unfortunately, there doesn’t seem to be a way to programmatically join a meeting as host when registration is required, as role=0 requires a valid registration, but hosts can’t register (error 3027). Is there still a way for the host to bypass the requirement and join nonetheless, ideally one that doesn’t involve using a random email address to register under as a regular participant? E.g. somehow parsing the “start_url” (which authenticates the host and joins the proper meeting automatically when pasted in a browser, but which doesn’t help in my case of constructing a meeting URL)?
Error? No explicit error, but join process is stuck on meetingStatus = 1 if role=0, or skips from meetingStatus = 1 to 3 if role=1.
Yes. The host can bypass participant registration, but the supported path is to join as the host, not as a role 0 participant. Zoom’s Meeting SDK uses a role 1 signature plus the host’s ZAK token to start the meeting as that Zoom user. Registration tokens are for the participant join path.
So you should not register the host under another email or try to extract a registration token from start_url. Retrieve the host’s ZAK using the Get User Token flow, generate the Meeting SDK signature with role 1, then pass that ZAK when joining through the SDK. Zoom explicitly documents this as the programmatic equivalent of giving the host their start_url.
The important distinction is that this starts/hosts the meeting. Zoom does not document a separate way for the meeting’s host to enter a registration-required meeting as a role 0 participant while bypassing registration. If role 1 is currently dropping from meeting status 1 to 3, verify that the ZAK belongs to the actual host and is being supplied through the host authorization flow.
Recall.ai’s Meeting Bot API can handle the meeting-platform integration layer.
Yes, I agree that that would be the logical consequence, but I cannot even start a meeting with role:1. My app is not designed to do that, but even when removing all the roadblocks, I still get the failure of meetingStatus 1->3. I have also tried starting a brand-new meeting without registration and added the scope user:read:token (although I have previously only seen this when using OBF tokens, which I don’t use at all). The only time the join succeeds under role=1 is when I under my own developer login and attempt to join my own meeting. It doesn’t work for any other beta-testers attempting to join/start a meeting.
Any idea what other issues there might be that I’m missing?