For all registration-related events (e.g. meeting.registration_cancelled), the value of payload.object.registrant.id didn’t appear to map to an actual Zoom user ID, even in the cases where a registered user is logged into their Zoom account prior to registration (the user I used in this test was not in the same Zoom org as my developer account, not sure if that matters). Is that expected?
Ideally, this ID would map to the Zoom user ID (i.e. the ID returned by the Get a User endpoint). This might allow applications like ours to route these events to the user who submitted the registration, so they can operate on these events programmatically (for example, I may want to get a Slack message when the status of my registration request changes).
Which App Type (OAuth / Chatbot / JWT / Webhook)?
OAuth, user-managed app.
How To Reproduce (If applicable)
Steps to reproduce the behavior:
- Create a user-managed OAuth application, configuring Event Subscriptions and sending Meeting Registration Cancelled to a URL endpoint.
- Create a new meeting, requiring registration.
- In a separate Zoom account, register for the meeting using the registration URL from step 2.
- Cancel the registration for this user.
- The meeting.registration_cancelled webhook payload will contain a registrant ID, but that ID does not map to the Zoom user ID for the user who submitted the registration in step 3.