Inconsistent email display for authenticated users having the same `account_id`

Starting March 01, 2022, Zoom changed the email address display rules. That’s okay, we knew about it on past February, by means of an RSS subscription.
On March 09, 2022, our QA confirmed and approved the current display rules were working for all our authenticated users.
However, our QA found a recent change regarding authenticated users having the same Zoom account_id but dealing with different domains in their respective email address.
By March 09, 2022, all these authenticated users were displaying the user_email email value when consuming the past participant meetings endpoint.
Recently, not all these authenticated users are displaying the user_email, regardless all of them are sharing the same account_id with the host_id.
Seemingly, this sounds like a recent change on Zoom’s side operating after March 01, 2022, by the time the aforementioned display rules took place.

Get past meeting participants endpoint is not displaying emails for authenticated users sharing the same account_id with the host_id when the domain in the email address differs, but this case was tested and approved by our QA on March 09, 2022, after the display rules changes were applied.

Zoom App
Zoom webhook notification dealing with the meeting.participant_joined and meeting.participant_jbh_joined events.

Endpoint affected by the inconsistency:

Steps to reproduce the behavior:

  1. Create a calendar invitation using one of Zoom’s calendar integrations (Outlook or Google Calendar). Invitees must share the same Zoom account_id. Invitees must have a valid email, every email is registered in the respective users account in Zoom, but the email domain differs among them.
  2. All invitees must authenticate in order to join the Zoom meeting.
  3. Not all authenticated participants are displaying an email address in aforementioned webhook notifications and api endpoint.

Additional context
We have a feature about skipping further processing about certain meetings having a blocklisted domain in the users’ email.
For example, let’s say we don’t want to fetch any data dealing with users having an email which domain is In this case, we should skip completely any zoom meeting dealing with a user having an email like After the new display rules took place, our QA tested this scenario in March 09, 2022, and it worked as expected around the webhook events we mentioned above. The endpoint, already quoted, was also responding as expected by that time, but as of today it is not behaving consistently and that’s why we are posting here in order to find out what is the root cause of these sudden but unexpected results.

1 Like

Hi @RobertoSL ,

If all users are authenticated and logged in and this is requiring, can you please open a support ticket with these details and the following:

  • Account Id
  • Description - A clear and concise description of expected vs. actual API behavior.
  • App Type & App ( JWT/OAuth/ SDK /Chatbot / Webhook/ZoomApps)
  • Affected Endpoint(s) - Knowing the API endpoint/s can help us to identify your issue faster. Please link the ones you need help/have a question with.
  • Error - The full error message or issue you’re running into.
  • How To Reproduce (if applicable)
    • Steps to reproduce the behavior with screenshots and/or video to help explain your problem:
  1. Request URL / Headers (without credentials) / Body (Screenshot(s) and text format of input)
  2. Request Response & Full Error (Screenshot(s) and text format of output)
  • Additional Context (if applicable) - Add any other info about the problem needed (meetingId(s), uuid(s), participantId(s) etc.)

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