Hi Donte,
Thank you, these resources are great! It seems like there may be several ways to do this.
The Zoom user_id seems useful, but I am a little confused about how to go about using in this use case.
In Mapping join and leave of participants webhook events with users on our application - #6 by tommy , it seems like it is recommended to use the meeting registration:
You could use meeting registration to create a unique join URL for all of your users. Then you can map your users easier via the
registrant_idanduser_id.
However, our users would potentially be joining several Zoom meetings hosted by us and this approach seems like it is meant for registering a user for a specific meeting. It also seems like the user_id is temporary and just for the meeting. Using email might be the way to go, at least for reports for meetings, as it seems this would allow us to map which of our users attended a given meeting, but it seems like this post you recommended that it is mentioned that it is possible to get the list of users who are in the meeting, which would be really great. However, it seems like this might require use of the registrant_id and the registration endpoint, which I cannot tell if it would work for our use case.
Do you have any advice for going about this? Thanks!