I’m running a project that depends on the Zoom API especially the call for the cloud recordings of a given meeting. On Saturday morning, April 1, when the release happened, our project started throwing errors because we use the meeting id field which was previously under the key “meeting_number” and is now “id.”
Although this was a simple fix to make, I just want to give the feedback that we are using this API and changes like that without notice can actually break our project. It would be nice to be able to know if a change like that is happening in advance or to have some way to access a version of the API that is stable.
We have checked the API https://zoom.github.io/api/#retrieve-a-meeting-s-all-recordings, and there are not any changes in April 1 release, so I think it’s the other problem about it, can you please provide more detail of your using? then we can confirm it is a regression or not
Here is the format of the API response I was getting before April 1. Starting the morning of April 1 it looks like “meeting_number” changed to “id”. It looks like the bug fix was the fact that there was a discrepancy between the API documentation and the actual API response?