Description
Previously, we had relied upon the API call `past_meetings/{meetingId}/participants to determine who attended the meeting. We used the e-mail addresses in the API response to identify the corresponding users in our own system.
We now find that some (but not all) e-mail addresses are returned as eg. 1kI5Li741W1iS1Aw6PwbGx7HcV2Nd54PAPfzp7ySvf7CunX18rQ9.YAxC393PbsVpD6XN@<correct hostname>
Error
There is no error, just values in the response-body that make no sense.
Which App Type (OAuth / Chatbot / JWT / Webhook)?
JWT
Which Endpoint/s? past_meetings/{meetingId}/participants
Questions
I would like to understand the following:
Is this “working as intended”? Will we continue to see these encrypted e-mail addresses going forward?
Is there a way to decrypt the <user>@ part back to the original e-mail address?
Not all e-mail addresses are encrypted; is this because e.g. client preferences, whether the client is a registrant for the meeting? Or put another way: what instructions could we give participants to ensure their e-mail address comes through unencrypted?
Should we start looking at webhooks - is the intended approach going forward that you collect attendance during the meeting, via webhooks?
Are there alternative API call(s) that we can use to recover the e-mail addresses of all attendees?
We’re still seeing the issue. For example meeting instance UUID OoI2RoqKRCiwhcF/WxUF3A== and T0MVZ3nnRx6YuvqsTC+duQ== have problems, while d2GtBrAjRbqQTv17DN5gZw== is OK.
Thanks @tommy! Although those particular meeting uuids aren’t necessarily the ones that we’re interested in as our users may pick others (and I wouldn’t want to keep bothering you with meeting uuids to patch). Would you happen to know which meetings this is a problem for and/or/whether the fix would be available across all meetings?
Those meetingUUIDs you share are now fixed. The fix is in place for all future meetings, and we are working on a patch for all previous meetings that were affected.
We are also seeing this issue on ZoomGov. Emails for recent meetings are unencoded, older meetings are encoded. Just wondering if these will ever come back. (same endpoints)