Our app uses webhooks to put participants in Zoom meetings onto a map in a virtual space. We currently listen for meeting.participant_joined
and meeting.participant_joined_waiting_room
for this. None of our meetings require registration, so I don’t believe there’s any registration going on.
We’ve noticed a few odd behaviors:
Sometimes the participant object in the webhook has an id
but no email
. From the docs it seems like this could happen when we get the meeting.participant_joined_waiting_room
webhook: if they’re not logged in, and they join a waiting room, we’d get a random id, and no email (“If participant joins without logging into Zoom, the value of this field will be randomly assigned.”). Three questions:
- Is the documentation correct? Should we expect random ids when a user is not logged in and they’re joining a waiting room?
- Are there any other situations when we’d expect to get an
id
but noemail
? Could this ever happen inmeeting.participant_joined
? - What is the rational behind the random ids when a participant joins a waiting room?
We’ve also noticed that we sometimes get a participant object with an email
, but no id
. This situation doesn’t seem to be referenced by the docs (I have a pair of join/leave webhooks that exhibit this issue that I can share privately). The docs for email
say the following:
Email address of the participant. This field is returned if the participant joined the meeting by logging into their Zoom account.
Given this, I would expect to always have an id
whenever I have an email
, and would expect this to be true for joining and leaving both meetings and waiting rooms.
- Should we ever expect to get
email
without anid
in these webhooks? If so, in what situations should we expect to get this?
Thanks,
Dave