I run a project that uses the Zoom API that supports students viewing lectures/class meetings that were recording on Zoom.
Currently there is no way to pin your project to a stable version of the Zoom API. Version 1 of the API is no longer in use, and Version 2 is currently being developed on.
The issue is that any time there is a release on Version 2 this potentially changes the API calls that we are making in production in our project. It has happened many times that our project breaks because of a change in the Zoom API and we need to rush to push out a fix. And over time the Zoom API has improved a lot! But…
Yes, there are release notes, but there’s no way for us to know which changes are coming in advance so that we can test them with our project.
It would be great if we had versioning within version 2 of the Zoom API so that we could use a stable version of the API in our project. Then, when a release happens we could test it in our development environment, and then update our production environment to use the latest version of the API once it has been tested thus hopefully avoiding major failures in production.