Description
Our users register to our meetings using our internal registration tool. We are not using Zoom’s registration, but rather we call the “Add Meeting Registrant” endpoint to add our users to meetings. This means that currently we can only track users which join by the participant_url which we get in response to “Add Meeting Registrant” endpoint, but some of our users join by typing in the Meeting Id/Passcode manually or through a phone call, and in those cases the participant joined/left webhooks don’t provide a registrant id that we can link back to the users of our platform.
We are looking for solutions on how to increase coverage of the tracking so we can make sure certain users of our platform attend the meetings without having a human have to validate it manually.
One of the potential solutions we thought of, but haven’t managed to test is using participant_pin_code as the meeting join password which is supposed to be provided by Add Registrant endpoint (it’s in the response in the docs) and we haven’t found a way to provide that participant_pin_code ourselves either.
If you require only authenticated (logged in) users join your meetings, you would be able to get more consistency with registrant id values. Is that possible for you to implement?
Hi @gianni.zoom, we are already using registrant id values and that works great for users which use the URL which gets returned by the registration endpoint. The problem is we don’t get them for users joining by phone number, or those joining by typing in the meeting id and password manually.
That’s what I mean to suggest: to disable those options and allow only authenticated (logged into client) users to join the meeting to be able to better track via registrant id. Currently, I don’t believe there’s another way to go around dialed in or users who enter the meeting info via the web ui to join.
Thanks for the answer @gianni.zoom. Yeah, that won’t work for us, we have quite a few users who use both those options. Do you maybe know how to get the participant_pin so we could maybe try using that as a password when joining from a phone? I am thinking that the registrant id might be sent then, but we were unable to test it as we can’t get the pin.
Hi @bornasm ahh I see! When you list registrants, the participant_pin_code is returned in the response body. Since it’s used to “authenticate audio participants before they join the meeting”, would this allow you to enable only authenticated participants to join so you can still track them?
While this Dashboard endpoint doesn’t include participant_pin_code, it does have registrant_id and audio_call object information at the bottom of the response body: Zoom Meeting API
Hi @gianni.zoom, I tested the list registrants endpoint , but there’s no participant_pin_code in the response. Do I have to somehow provide it to Zoom and if yes how?
Hi,
I am running into a similar issue when using the Zoom connector in Tray. I am trying to register participants for a meeting using the batch_registrants endpoint and it seems to succeed, but the participant_pin_code is not returned:
