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:
I hope that helps! Let me know if you have any questions.
Thanks,
Max