Add Participant UUID to participant objects in webhooks

Feature Requests
1

Is your feature request related to a problem? Please describe.
Zoom Apps requires we pass the new “Participant UUID” to call the various functions however the webhooks we use in tandem with zoom apps does not provide this field in the “particpant” object it returns.

This means we have to implement complicated logic to tie these users back to the webhooks they are associated with.

In order to associate a participant registered via a webhook with the participantUUID I need to:

  1. Receive the webhook with the participant.
  2. Save the participant with the participant ID and associated information.
  3. Wait for an owner user to load the zoom app.
  4. Update that same participant record with the participant UUID.

Describe the solution you’d like
I would like the participant UUID to be passed in all participant objects returned by webhooks or other apis to contain the new participant UUID. Ideally the field would be “uuid” or “participant_uuid” .

 object: {
             uuid: 'oenoewijoijewoirwer==', // MEETING UUID 
             host_id: 'klmlsjdasdsd',
             participant: {
                  user_id: '123456789', // participant ID 
                  uuid: '4C81FD78-DF2F-4BA8-B833-0FB7EF29BCA3', // <- REQUESTING THIS... = participantUUID
                  participant_user_id: 'jnjnewqeqwe'
                  ...
             },
},

There’s a number of webhooks where a “participant” object is returned. I think it makes sense to add this to all of them though the ones below are priority.

Priority
meeting.participant_joined
meeting.participant_left
meeting.participant_joined_breakout_room
meeting.participant_joined_waiting_room
meeting.participant_left_breakout_room
meeting.participant_left_waiting_room

All participant webhooks
meeting.participant_admitted
meeting.participant_feedback
meeting.participant_jbh_joined
meeting.participant_jbh_waiting_left
meeting.participant_jbh_waiting
meeting.participant_phone_callout_accepted
meeting.participant_phone_callout_missed
meeting.participant_phone_callout_rejected
meeting.participant_phone_callout_ringing
meeting.participant_put_in_waiting_room
meeting.participant_role_changed
meeting.participant_room_system_callout_accepted
meeting.participant_room_system_callout_failed
meeting.participant_room_system_callout_missed
meeting.participant_room_system_callout_rejected
meeting.participant_room_system_callout_ringing

Describe alternatives you’ve considered
Currently I store the participant ID and then update with the participant UUID when the zoom apps when the app loads.

Additional context
Zoom Apps has deprecated participant ID in favor of participant UUID. According to this we are not supposed to be using participant ID in zoom apps. Here is the related post about the subject.

1 Like