Issues with Swagger

Description/Error

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

Which Endpoint/s?
current swagger file
2019/11/11 https://marketplace.zoom.us/docs/api-reference/zoom-api/Zoom%20API.oas2.json

How To Reproduce (If applicable)

  1. goto https://editor.swagger.io/
  2. paste json body
  3. See error

Screenshot in attachment

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

Hey @a.koval,

Thanks for letting us know. As a work around, we have (beta) client libraries and updated swagger files here:

https://drive.google.com/drive/folders/1JfxC7Ybla3wc0xTpPAXMvO_g5n6m_TZM

Feel free to test them out!

Thanks,
Tommy

Hey @a.koval,

We fixed the issues, but you still have to use the online editor and convert to Open API3.

Thanks,
Tommy

Hello, Tommy!

(beta) client libraries

  • is concept, not useful code.
    Inside your google disk folder I’m not found “…updated swagger files”

Hey @a.koval, apologies you did not find the Client Libraries useful.

We fixed the issues in the swagger file, but you still have to use the online editor and convert to Open API3.

Thanks,
Tommy

  • GET /accounts/{accountId}/settings lost “schema” item (example item - Ok)
  • GET /webinars/{webinarId}
    example have invalid field value “id” - int
  "id": 00000011110,
  "join_url": "https://zoom.us/j/00000011110",

Hey @a.koval,

Thanks for pointing this out, we will fix it.

As for the invalid value for webinar id, what do you mean it is invalid?

-Tommy

“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.

Hey @a.koval,

Thanks for the clarification, we will get this fixed!

-Tommy

Hey @a.koval,

The swagger issues should be fixed!

Thanks,
Tommy