| Status | ||||||
|---|---|---|---|---|---|---|
|
...
- Meetings chat archiving is not supported
- Webinars are not supported
- Video files for Meeting recordings might not match the time interval defined by the join and leave events of the recorded users. The Zoom recording process currently starts when the first recorded user joins and ends when the meeting ends. The recording system creates CDRs for each recorded user based on their join/leave events but will link the full video files to these records. Audio files are created individually for each recorded participant (individual recording has to be enabled on the Zoom side) and are not affected by this limitation.
- The APIs published by Zoom are tenant/account level APIs (not user level), which means that the API response will include information about recordings for all configured users in the tenant. The system filters the response based on the configured users and does not attempt to download recordings for users not configured in the system. When multiple systems are deployed to allow data segregation, this approach introduces some overhead as unnecessary data is downloaded (and discarded).
- Due to Zoom API rate limits and lack of filtering for specific users, large tenants might unable to use the CDR reconciliation feature for Zoom Meetings, because the process requires to call resource-intensive APIs for every meeting in the tenant.
- Meetings hosted by external users (users outside of the customer tenant/account) can only be archived with limitations. The participant information is limited to the recorded users in the customer tenant, no external participants or non-recorded internal participants will be stored.
- Meeting recordings always include an MP4 video file (in addition to the M4A audio file) even if no camera was used or screens sharing was not enabled. The video contains a black screen with the name of the users in the center. When the recorded user is configured for voice-only recording/archiving, the system only imports the M4A audio file. If the recorded user is configured for video and/or screen share recording, the system imports the MP4 file as well and sets the modality to Screen & Application Share (regardless if video and screen share was used).
- Redundant deployments are supported but multiple servers will run independently and attempt to import the same recordings and multiplicate the Zoom API usage. The system will eventually import only one copy of the same call and meeting. For the same reasons, load balancing is not recommended, while supported.
- The Zoom Phone API does not support Archiving time for filtering which introduces an overhead in querying the data and the system has to query the same time interval multiple times.
- The reconciliation process for Zoom Phones only queries records where the recording_id is set.
- CDR reconciliation is not supported for breakout rooms.
Version support
Switch Name & Model | Zoom Meetings Zoom Phone |
|---|---|
Supported Versions | Contact Zoom |
Supported Endpoint / DeviceTypes | All |
...
API | Zoom API Limit (Business+) | Usage | Estimation | |
|---|---|---|---|---|
| Phone | /phone/recordings https://marketplace.zoom.us/docs/api-reference/zoom-api/phone/getphonerecordings | 20 req. / second | Import | Used in every policy scheduling, multiple times if call count is high. Safe estimate per policy run: max(Recorded calls since last run / 300; 1) * 4 |
/phone/call_logs https://marketplace.zoom.us/docs/api-reference/zoom-api/phone/accountcalllogs | 40 req. / second Daily limit of 60,000 requests/day shared by heavy & resource-intensive APIs. | CDR reconciliation | Used in every policy scheduling, multiple times if call count is high. Safe estimate: max(Total calls since last run / 300; 1) * 4 | |
| Meeting | /archive_files https://marketplace.zoom.us/docs/api-reference/zoom-api/archiving/listarchivedfiles | 60 req. / second | Import | Used in every policy scheduling, multiple times if Meeting count is high. Safe estimate per policy run: max(Recorded meetings since last run / 300; 1) * 4 |
/metrics/meetings/{meetingId}/participants https://marketplace.zoom.us/docs/api-reference/zoom-api/dashboards/dashboardmeetingparticipants | 20 req. / second Daily limit of 60,000 requests/day shared by heavy & resource-intensive APIs. | Both import and CDR reconciliation | Import: Used once per archived meeting on Zoom side, might call multiple times in rare cases, safe estimate: archived meeting * 2 Reconciliation: Used once per all meetings in the whole tenant (not just for recorded meetings), might call multiple times in rare cases, safe estimate: total meeting * 2 | |
/metrics/meetings https://marketplace.zoom.us/docs/api-reference/zoom-api/dashboards/dashboardmeetings | 20 req. / second Daily limit of 60,000 requests/day shared by heavy & resource-intensive APIs. | CDR reconciliation | Used in every policy scheduling, multiple times if Meeting count is high. Safe estimate per policy run: max(Total meetings since last run / 300; 1) * 4 |
Types of import that are subject to daily API limit:
- Zoom Phones: no
- Zoom Phones with CDR reconciliation: yes
- Zoom Meetings: yes
- Zoom Meetings with CDR reconciliation: yes
Some examples of how much volume of traffic a daily rate limit of 60 000 can safely handle when scheduling the import for every 5 minutes:
- Zoom Phones: no limit
- Zoom Phones with CDR reconciliation: 4.5 million calls daily
- Zoom Meetings: 30 000 meetings daily
- Zoom Meetings with CDR reconciliation:29 000 meetings daily
- Zoom Meetings and Zoom Phones: combined traffic of any amount of daily calls and 30 000 meetings
- Zoom Meetings and Zoom Phones both with CDR reconciliation: combined traffic of 2.2 million daily calls and 14 500 meeting
Zoom Meeting metadata
The system captures the following metadata specific to Zoom meetings.
...