Developer impacting changes during COVID-19
Zoom Developer Documentation Survey
Please take a few minutes to fill out the Zoom Developer Docs survey and let us know how we can assist you better with our docs. Your input will be invaluable in improving our documentation.
Delayed responses by Zoom staff on developer forum due to volume of posts. Expect a reply in 24 hours on weekdays.
What does this mean?
During these tough times, we are seeing a massive increase in demand for our services. To continue serving our incredible services to our customers and developers, we may be making changes rapidly. Most of these changes will be temporary but we will make sure to note that below.
This is an open thread, and we welcome all feedback below.
Staff Response Times
In order to provide quicker response times to everyone’s questions, we are encouraging escalations and issues with sensitive information to email developersupport@zoom.us instead of Private Messaging Zoom Staff on the Devforum. Moving forward, Private Messages will be turned off on the Devforum since they are not monitored by all Zoom Staff and are difficult to track.
When to use the Devforum:
- To search for existing solutions to your issue
- For posting Zoom Developer Platform questions without any sensitive information needed for us to assist (similar to Stackoverflow)
You can expect your first reply from a staff member on the Devforum in 24 hours on weekdays.
List of developer impacting changes
| Change | Summary | Date Changed | Temporary |
|---|---|---|---|
| Webhook retry logic is has been reenabled | We will be temporarily disabling the retry logic for all webhooks. This means if the webhook fails to send, or does not receive a 200 OK response from your server, we will not try to send that respective webhook again. (Reenabled) | 06/06/2020 | No |
| Zoom 5.0: Update required for GCM encryption | A system-wide account enablement of GCM encryption for real-time content will occur on May 30, 2020. Click here for instructions on upgrading to the latest SDKs. | 5/30/2020 | No |
| Recording download url within Webhook payload changed to 180 characters | To align with Zoom’s recent announcement pertaining to our 90 day security initiative, we will be changing the download recording url from 120 characters to 180 characters. This may cause a breaking change if you have already saved download links within your database within a column that can’t more that than around 120 characters. A workaround would be to adjust your Database column to hold at least 256 characters. | 4/28/2020 | No |
| (Possible Breaking Change) Passwords for Meeting/Webinar and Recording strength increase | To align with Zoom’s recent announcement pertaining to our 90 day security initiative, we will be releasing breaking changes to our APIs related to the new password requirement settings within the account setting page. This new setting allows Account owners and admins to set Meeting password and Recording password requirements. This change will affect the following API endpoints if your current Meeting or Recording passwords do not follow the new password requirement settings if enabled. POST /users/{userId}/meetings, PATCH /meetings/{meetingId}, POST/users/{userId}/webinars, PATCH /webinars/{webinarId}, PATCH /meetings/{meetingId}/recordings/settings | 4/27/2020 | No |
| 11-Digit Meeting and Webinar IDs | Scheduled meeting and webinar IDs will now support 11 digits to match product changes. Meeting IDs previously handled as integers should be handled as long data type (represented by int64 in JSON). | 4/12/2020 | No |
| WebSDK Unable to join some meetings (FIXED) | Unable to join meeting error fixed last night after cleaning cache. | 4/7/2020 | Yes |
| WebSDK 403 - Request Timeout & The service is temporarily error (FIXED) | Seen by hosts using waiting room feature, we are working on the fix, thanks for your patience. | 4/7/2020 | Yes |
| JWT/SDK Token invalid error (FIXED) | We are aware of the Invalid access token. when using a SDK / JWT Token to call the Zoom APIs. Our engineering team is working on fixing this issue and we will update the status here once the issue is resolved. Thank you for your patience. |
4/6/2020 | Yes |
| Create JWT App Error (FIXED) | We are aware of the api_credentials_not_found error being caused while users are attempting to create a new JWT app. Our engineering team is working on fixing this issue and we will update the status here once the issue is resolved. Thank you for your patience. | 4/5/2020 | No |
| (Possible Breaking Change) Chatbot Email Message Type Removed | To avoid phishing attacks, using the mailto: protocol as the “link” parameter in a chatbot message will no longer display the message. The API call will now return an error code 7001: Invalid request body format. This change will affect the following API endpoints: POST /im/chat/messages | 4/4/2020 | No |
| Recent API Backward Incompatible Changes | To ensure reliability of our service, we have made some backward incompatible changes in our APIs in accordance to the changes in our product. The these changes will take effect starting April 03, 2020, unless otherwise noted. For more details you can visit our Developer Announcement page and Changelog page | 4/3/2020 | No |
| Some call logs could be missing from last 7 days | The DB table for call logs exceeded the maximum size limit of 10 GB. A new DB table was created on Production since this early morning. | 03/25/2020 | NA |
| Sunset of V1 APIs pushed back | Due to the recent events of COVID-19 we are extending the life of the v1 APIs and we will be shutting down the Zoom v1 APIs and any associated apps on May 31st 2020. | 05/31/2020 | NA |
Please follow this thread for the latest status updates about the Zoom Developer Platform.
