Errors
Hide
Semantic error at paths./im/users/{userId}/channels
Declared path parameter "userId" needs to be defined as a path parameter at either the path or operation level
Jump to line 22664
Structural error at paths./rooms/account_settings.get.responses.200.schema
should NOT have additional properties
additionalProperty: oneOf
Jump to line 27280
Structural error at paths./rooms/account_settings.patch.parameters.0.schema
should NOT have additional properties
additionalProperty: oneOf
Jump to line 27513
Structural error at paths./rooms/locations/{locationId}/settings.get.responses.200.schema
should NOT have additional properties
additionalProperty: oneOf
Jump to line 28096
Structural error at paths./rooms/locations/{locationId}/settings.patch.parameters.0.schema
should NOT have additional properties
additionalProperty: oneOf
Jump to line 28362
Structural error at paths./rooms/{roomId}/settings.get.responses.200.schema
should NOT have additional properties
additionalProperty: oneOf
Jump to line 28879
Structural error at paths./rooms/{roomId}/settings.patch.parameters.1.schema
should NOT have additional properties
additionalProperty: oneOf
Jump to line 29129
Here mixed up the syntax from Swagger 2.0 with Openapi 3.0.0
In the online editor you can click on the button Edit > Convert to OpenAPI 3 to use Openapi 3.0.1
unfortunately some errors will stay
Errors
Semantic error at paths./phone/users/{userId}/status
Declared path parameter "userId" needs to be defined as a path parameter at either the path or operation level
Jump to line 381
Semantic error at paths./im/users/{userId}/channels
Declared path parameter "userId" needs to be defined as a path parameter at either the path or operation level
Jump to line 33021
Semantic error at paths./phone/users/{userId}/online_calls
Declared path parameter "userId" needs to be defined as a path parameter at either the path or operation level
Jump to line 35468
Semantic error at paths./metrics/client/satisfaction.get.requestBody
GET operations cannot have a requestBody.
Jump to line 42909
“application/json”
RFC4627 … int = zero / ( digit1-9 *DIGIT )
The representation of numbers - integer has value 00000011110
which contains leading zeroes (and it’s not the string)
Any Json-validator produce error.
Clear the default text from the editor using File-> Clear Editor.
Load the Zoom API specification by using File-> Import file. Browse to the file you downloaded, then press Open.
The file loads in the editor. After a moment, a number of errors will be seen in the right pane. Ignore these for the moment.
Select Edit-> Convert to OpenAPI 3, then press Convert. When the conversion has finished, press Close.
Wait a few moments while the editor parses the file and checks for any errors.
== ACTUAL RESULT ==
The following errors are displayed:
Semantic error at paths./im/chat/messages/{message_id}.delete.requestBody
DELETE operations cannot have a requestBody.
Jump to line 32995
Semantic error at paths./meetings/{meetingId}/batch_registrants
Declared path parameter "meetingId" needs to be defined as a path parameter at either the path or operation level
Jump to line 47023
Semantic error at components.securitySchemes.Client Credentials
Component names can only contain the characters A-Z a-z 0-9 - . _
Jump to line 59386
Hi @sendres The JSON spec for some of our APIs do not match the Open API standard. We will be fixing this issue in the future but do not have a timeline yet.
Thank you @shrijana.g. The university where I work is driving toward increased automation and interoperation of our core learning technologies, including Zoom. With a well-formed OpenAPI specification, our developers can generate clients in whatever language they prefer and our systems people can use Microsoft Power Automate to generate a custom connector for Zoom.
To be blunt, the biggest roadblock we have found is vendors whose specs don’t comply with OpenAPI standards. I’m working to generate Python and Power Automate clients for five platforms right now. In each case, I was able to download the vendor’s JSON spec only to find it fails compliance with the standard.
I strongly encourage Zoom to make OpenAPI compliance testing part of their API release process. As we can see from earlier posts in the thread, previous releases have had similar issues. I appreciate your work to fix this but am at the same time annoyed that we as customers are having to deal with these problems.
