You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 text was updated successfully, but these errors were encountered:
lfpll
pushed a commit
to lfpll/tap-zoom
that referenced
this issue
Dec 13, 2022
* Build the merge-into-bq job with a dedicated GHA workflow
* Remove the merge-into-bq build from the Development workflow
* Add label to the merge-into-bq Docker image to cause a rebuild
* Hack GHA workflow to push the merge-into-bq job image tagged with `latest`
* Publish production docker images to the analytics-warehouse-production project
* Change production DWH project and dataset for the masterdata layer
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}/registrants
should includeoccurrence_id
query param./past_meetings/{meetingId}/polls
Polls should be updated to instance-aware endpoint, using UUID formeetingId
./meetings/{meetingId}/registrants
should includeoccurrence_id
query param./report/meetings/{meetingId}
Use instance UUID asmeetingId
instead of the meeting ID./report/meetings/{meetingId}/participants
Use instance UUID asmeetingId
instead of the meeting ID.Webinars
/webinars/{webinarId}/registrants
should includeoccurrence_id
query param./past_webinars/{webinarId}/polls
Polls should be updated to instance-aware endpoint, using UUID forwebinarId
./webinars/{webinarId}/registrants
should includeoccurrence_id
query param./report/webinars/{webinarId}
Use instance UUID aswebinarId
instead of the webinar ID./report/webinars/{webinarId}/participants
Use instance UUID aswebinarId
instead of the webinar ID.Risks
The text was updated successfully, but these errors were encountered: