The tap only pulls information on the latest webinar instance, excluding past instances of meetings/webinars.
A webinar, like a meeting can be reused. Each use creates an instance with a UUID. There are several Zoom API calls that take either an instance UUID, or a meeting/webinar ID. If a specific instance is not requested, the latest instance is returned.
Expected Zoom API Usage
The tap should query the pastwebinars and pastmeetings endpoints and wherever possible utilize the webinar/meeting UUID of the instance, instead of just the webinar ID when making other API calls. In some cases, there is a separate endpoint that should be used instead.
It should be tested that the endpoints labeled "past_meetings" are suitable for active meetings, or we will need to add a caveat that a meeting must have ended in order for it to be reported. I suspect despite the naming of these endpoints, the current meeting UUID can be queried, but this should be verified.
This will include a potentially large amount of historical data. For my purposes this is exactly what I want, though this may make it more important to add incremental key-based extraction and potentially a historical start date to restrict the a amount of history returned.
The tap only pulls information on the latest webinar instance, excluding past instances of meetings/webinars.
A webinar, like a meeting can be reused. Each use creates an instance with a UUID. There are several Zoom API calls that take either an instance UUID, or a meeting/webinar ID. If a specific instance is not requested, the latest instance is returned.
Expected Zoom API Usage
The tap should query the pastwebinars and pastmeetings endpoints and wherever possible utilize the webinar/meeting UUID of the instance, instead of just the webinar ID when making other API calls. In some cases, there is a separate endpoint that should be used instead.
Meetings
meetings/{meeting_id}/registrantsshould includeoccurrence_idquery param./past_meetings/{meetingId}/pollsPolls should be updated to instance-aware endpoint, using UUID formeetingId./meetings/{meetingId}/registrantsshould includeoccurrence_idquery param./report/meetings/{meetingId}Use instance UUID asmeetingIdinstead of the meeting ID./report/meetings/{meetingId}/participantsUse instance UUID asmeetingIdinstead of the meeting ID.Webinars
/webinars/{webinarId}/registrantsshould includeoccurrence_idquery param./past_webinars/{webinarId}/pollsPolls should be updated to instance-aware endpoint, using UUID forwebinarId./webinars/{webinarId}/registrantsshould includeoccurrence_idquery param./report/webinars/{webinarId}Use instance UUID aswebinarIdinstead of the webinar ID./report/webinars/{webinarId}/participantsUse instance UUID aswebinarIdinstead of the webinar ID.Risks