Full participant data for webinars for a user-level OAuth App

Feature Requests
3

Hi @tommy,

We have taken a look at the Participant Joined Webhook and it does partially work for us, but here are its limitations:

  1. As well as setting up a link for a future webinar, we are hoping to allow clients to link webinars to events in our CRM after they have occurred and get a list of the participants into our tool. This would not be possible with the webhook but only if there is an endpoint.

  2. We are also concerned about the fragility of only working with Webhooks. What if our system is down for a minute, or if your webhook retries break (as they did a little while ago). If there was at least a past webinar participants endpoint then we would have a backup source for the data. ((As an aside: can you point me to any details about the webhook retries? When and how often does the retry occur?))

  3. For our clients, meetings and webinars are just two different options, they don’t see them as categorically different, so to have disparate functionality between the two entities for our integration will cause problems. We would have to have disparate functionality because the ParticipantJoined Webhook for meetings does not allow for matching between participants and registrants, like the webinar does, as you note here

So all in all it is quite inconsistent to not have one and it causes us significant difficulty in our attempt to integrate with Zoom. Do you therefore think it would be possible to get a webinar participants endpoint on your API team’s backlog?

Thanks,
NGPVAN/Everyaction Team

PS: There seem to be some errors in the API documentation:

image
image1258×202 87.4 KB

  1. The above helptext from the ParticipantJoined webhook Indicates that the ID in the participant object is the userID from the Users API, and that it only shows if the person logs into zoom. However, our testing (and other comments) show that this ID is the RegistrantID from the registration record and that when you enter the meeting by clicking the tokenated link from the registration confirmation email then you always have this value, whether you are previously signed-in to Zoom or not. This is very good, though, because if the registrationID did not display in the Participant Joined Webhook, there would be no way to match the participant to the registrant, since User_Email is not there. So I am definitely not complaining about the functionality, but I wanted to alert you that the API reference note is not correct!

  2. The Participant UUID field in the Past Meeting Participants Endpoint actually seems to function like the helptext in the ParticipantsJoined webhook but that is not indicated as such.