IMPORTANT notice about reporting endpoints and participant identifiers in the Meeting API

Shariq
Tue, 07 Mar 2023 19:25:48 +0000
API and Webhooks

Earlier this week, there was a change to the Meeting API that affected the responses from the Dashboard and Reporting endpoints. We have compiled a list of questions that will hopefully give everyone a sense of how this change will affect them and what to expect going forward.

Read the original announcement about the Dashboard and Reporting changes.

What gives?! Why was there no notice on this change?

The nature of this change didn’t trigger Zoom’s regular change protocols, but as we can see, this has had an unexpected impact on our customers. We apologize for the inconvenience and disruption.

What can I, as a developer, expect from now on?

After hearing feedback from you, we have rolled back some of the changes. Developers will be able to access the registrant_id value again. The id and participant_user_id fields will be null for meeting guests (but not the host).

I have application logic that depends on the participant_user_id or id. What field should I use instead?

You should key your logic off of the registrant_id value. This value will be filled in independent of whether the guest is a member of the app’s Zoom account or not. If this doesn’t fulfill your needs, please take a look at the email display rules to get a better understanding of what is available for your use-case.

How will this impact webhooks?

Right now, webhook responses will contain id and participant_user_id but this behavior will be turned off by the end of March 2023. We recommend keying any logic off of the registrant_id value, which is available in the webhook response.

20 posts - 9 participants

Read full topic