Participant join/left webhook doesn't send occurrence id as well as actual meeting session start time for recurring meeting

[pritam1 (Pritam)]

Description
Webhook doesn’t send occurrence id as well as actual meeting session start time. Then how can we identify which occurrence participants are joining or leaving?

Error
Say I have created a recurrence meeting which has 3 occurrences with the start time 4 PM. Now by UUID I can find out easily the first occurrence. Now at 7 PM, I want to host tomorrow’s call then the participant joins the webhook sends today’s start date and a different UUID. Without occurrence Id how can we identify which occurrence that user is presently hosting?

Which App Type (OAuth / Chatbot / JWT / Webhook)?
participants webhook

Which Endpoint/s?
Webhooks:~~
meeting.participant_join
meeting.participant_left

How To Reproduce (If applicable)
Steps to reproduce the behavior:

1. Create meeting webhook returns occurrences with start date for recurrence meeting
2. Meeting join and the left doesn’t occurrence id

[MaxM]

Hey @pritam1,

Thank you for reaching out to the Zoom Developer Forum. This is a great question! It’s difficult to map occurrences to UUIDs for some of the same reasons that you mentioned here. For instance, let’s say we have the following meetings:

• occurrence 1: 03/01
• occurrence 2: 03/03
• occurrence 3: 03/05

Let’s say that the meeting hosts forgets to start the meeting on March 1st and then starts the meeting on March 2nd. It’s difficult to say which occurrence this belongs to. Is it 03/01 started late or is it 03/03 started early?

Further, let’s say that a host starts a meeting many times on March 3rd. There’s no way to say if they are starting the March 5th meeting early or not.

For this reason, we don’t recommend that you rely on mapping occurrence ID to UUID in your code. An occurrence ID should be used as a way to identify events that you’ve scheduled, but nothing more. After a meeting has started, it will have it’s own UUID and that should be used for accessing the meeting along with the start_time.

If your use-case requires that you map occurrence_id to UUID, you can use the timestamps along with custom logic in order to determine what occurrence each UUID belongs to. Please see the following forum post for more information:

Identifying past instances of reoccuring meetings

Hey @MelisaB and @bensw, Thank you for reaching out to the Zoom Developer Forum. Our internal team indicated that there isn’t a relationship between Occurrence ID and Meeting UUID so this isn’t a feature they would be able to add. This is because, as you’ve seen, if a meeting is started at the wrong time, early or late, then it’s impossible to say if this was an occurrence of a previous meeting or a future meeting. When a meeting occurrence ends, the occurrence gets its own Meeting instance U…

I hope that helps! Let me know if you have any questions.

Thanks,
Max

[pritam1 (Pritam)]

Hi @MaxM , Thanks for the explanation. I have my answer now.
Just a thought:~ It would have been helpful if webhook participants joins/left webhooks also send the meeting occurrence assigned start time along with the time that occurrence host time. Presently it only sends occurrence host time now. We can easily map that occurrence by occurrence assigned start time.
Thanks

[MaxM]

Hey @pritam1,

I’m glad to hear that was helpful!

@pritam1

It would have been helpful if webhook participants joins/left webhooks also send the meeting occurrence assigned start time along with the time that occurrence host time.

If you would like this feature to be considered for a future release, I recommend posting in the Feature Requests category.

Thanks,
Max