Past Meeting Participants - Email addresses are encoded?

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?

Hey @james.alliance

Thanks for posting on the Zoom Devforum! I am still learning, but I will try my best to help answer your question. :slightly_smiling_face:

Checkout these related threads that may have the answer you are looking for:

If these threads did not help, please let us know by replying back here and someone from the Developer Relations team will get back to you shortly.

Thanks,
DeveloperBot

Sadly, these posts do not really address the issue I’m seeing.

Hey @james.alliance,

We are working to resolve this issue. I will keep you updated. (ZOOM-182022)

Thanks,
Tommy

Thanks Tommy!

I’m pretty new to Zoom (as a developer, at least). ZOOM-182022 looks like a JIRA issue… where can I find the JIRA instance where this issue lives?

Hey @james.alliance,

The Jira issue is for internal Zoom tracking. I will keep you updated here.

That being said, are you still seeing this issue with the encoded emails? Can you share steps to reproduce?

Thanks,
Tommy

We’re still seeing the issue. For example meeting instance UUID OoI2RoqKRCiwhcF/WxUF3A== and T0MVZ3nnRx6YuvqsTC+duQ== have problems, while d2GtBrAjRbqQTv17DN5gZw== is OK.

Similar threads:

For a meeting occurring in the past ~24 hours, this issue appeared to be resolved. Thanks again for following up :slight_smile:

1 Like

Hey @james.alliance,

Happy to hear you are seeing the issue resolved! :slight_smile:

Keep us updated if you run into any more issues.

Thanks,
Tommy

Hey @danny,

Thanks, I will get those meeting uuids patched.

-Tommy

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?

Hey @danny,

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.

Thanks,
Tommy

Thanks very much @tommy, great to hear that a patch is coming for all meetings and that it’s not a problem for future meetings :slight_smile:

1 Like

You are welcome! :slight_smile:

-Tommy

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)

Hey @jamesd,

Can you please reach out to developersupport@zoom.us for more details about the issue?

If you could provide the endpoints you are seeing the issue with that would help us investigate.

Thanks,
Tommy

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.