# Issues with Swagger

**URL:** <https://devforum.zoom.us/t/issues-with-swagger/7027>\
**Category:** API and Webhooks\
**Created:** [December 11, 2019, 7:40pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027 "2019-12-11T19:40:25Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![a.koval](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/a.koval/32/2585_2.png) [@a.koval](https://devforum.zoom.us/u/a.koval)\
**Post date:** [December 11, 2019, 7:40pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/1 "2019-12-11T19:40:26Z")

</div>

**Description/Error**

```auto
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](https://marketplace.zoom.us/docs/api-reference/zoom-api/Zoom%20API.oas2.json)

**How To Reproduce (If applicable)**

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

**Screenshot in attachment**

 ![Снимок экрана 2019-12-11 в 22.38.48](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/2X/3/3736591a3f42cb4d507d4fcf9cdd93abd8eada31.png)

---

<div class="post-metadata">

**Author:** ![a.koval](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/a.koval/32/2585_2.png) [@a.koval](https://devforum.zoom.us/u/a.koval)\
**Post date:** [December 11, 2019, 8:01pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/2 "2019-12-11T20:01:32Z")

</div>

Here mixed up the syntax from `Swagger 2.0` with `Openapi 3.0.0`

In the [online editor](https://editor.swagger.io/) 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
```

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [December 11, 2019, 9:18pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/3 "2019-12-11T21:18:23Z")

</div>

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](https://drive.google.com/drive/folders/1JfxC7Ybla3wc0xTpPAXMvO_g5n6m_TZM)

Feel free to test them out!

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [December 11, 2019, 9:55pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/4 "2019-12-11T21:55:45Z")

</div>

Hey @a.koval,

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

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![a.koval](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/a.koval/32/2585_2.png) [@a.koval](https://devforum.zoom.us/u/a.koval)\
**Post date:** [December 12, 2019, 8:27pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/5 "2019-12-12T20:27:54Z")

</div>

Hello, Tommy!

> (beta) client libraries

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

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [December 12, 2019, 8:33pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/6 "2019-12-12T20:33:43Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![a.koval](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/a.koval/32/2585_2.png) [@a.koval](https://devforum.zoom.us/u/a.koval)\
**Post date:** [December 17, 2019, 8:34am UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/7 "2019-12-17T08:34:05Z")

</div>

- GET /accounts/{accountId}/settings lost “schema” item (example item - Ok)
- GET /webinars/{webinarId}  
example have invalid field value “id” - int

```auto
  "id": *********** ,
  "join_url": "https://zoom.us/j/00000011110",

```

\*This post has been edited to remove any meeting / webinar IDs

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [December 17, 2019, 4:52pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/8 "2019-12-17T16:52:19Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![a.koval](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/a.koval/32/2585_2.png) [@a.koval](https://devforum.zoom.us/u/a.koval)\
**Post date:** [December 18, 2019, 7:15am UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/9 "2019-12-18T07:15:01Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [December 18, 2019, 9:24pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/10 "2019-12-18T21:24:15Z")

</div>

Hey @a.koval,

Thanks for the clarification, we will get this fixed!

-Tommy

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [December 18, 2019, 11:33pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/11 "2019-12-18T23:33:54Z")

</div>

Hey @a.koval,

The swagger issues should be fixed!

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![praveenkh48](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/praveenkh48/32/6882_2.png) [@praveenkh48](https://devforum.zoom.us/u/praveenkh48)\
**Post date:** [April 24, 2020, 3:01am UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/12 "2020-04-24T03:01:26Z")

</div>

Did you changed the API that not to accept RequestBody as input of any swagger API changes ?

I saw you have used the beta client libraries, could you please share those.

---

<div class="post-metadata">

**Author:** ![a.koval](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/a.koval/32/2585_2.png) [@a.koval](https://devforum.zoom.us/u/a.koval)\
**Post date:** [April 24, 2020, 7:03am UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/13 "2020-04-24T07:03:50Z")

</div>

I don’t any use beta clients. I am using golang code generation based on swagger contract. Unfortunately, I can’t share my code (employer obliged me). But I can expand the list of tools used:  
“[github.com/antchfx/jsonquery](http://github.com/antchfx/jsonquery)”  
“[github.com/tidwall/gjson](http://github.com/tidwall/gjson)”  
“[github.com/gedex/inflector](http://github.com/gedex/inflector)”  
“[github.com/idubinskiy/schematyper/stringset](http://github.com/idubinskiy/schematyper/stringset)”  
“[github.com/go-openapi/inflect](http://github.com/go-openapi/inflect)”

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [April 27, 2020, 9:30pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/14 "2020-04-27T21:30:37Z")

</div>

Hey @praveenkh48,

I am unaware of any such changes.

The [beta client libraries](https://drive.google.com/drive/folders/1JfxC7Ybla3wc0xTpPAXMvO_g5n6m_TZM?usp=sharing) are now 6 months outdated. We are working on the Swagger spec to work out of the box soon.

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [April 27, 2020, 9:30pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/15 "2020-04-27T21:30:49Z")

</div>

Thanks for sharing these @a.koval! 🙂

-Tommy

---

<div class="post-metadata">

**Author:** ![sendres](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sendres/32/3793_2.png) [@sendres](https://devforum.zoom.us/u/sendres)\
**Post date:** [June 20, 2020, 3:58pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/16 "2020-06-20T15:58:08Z")

</div>

I am seeing the following problem when attempting to use the Zoom API version 2.0.0 in Swagger Editor:

== STEPS TO REPRODUCE ==

1. Downlocad the Zoom API specification from [https://marketplace.zoom.us/docs/api-reference/zoom-api/Zoom%20API.oas2.json](https://marketplace.zoom.us/docs/api-reference/zoom-api/Zoom%20API.oas2.json).
2. Open the online Swagger Editor at [https://editor.swagger.io/](https://editor.swagger.io/).
3. Clear the default text from the editor using File-\> Clear Editor.
4. Load the Zoom API specification by using File-\> Import file. Browse to the file you downloaded, then press Open.
5. 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.
6. Select Edit-\> Convert to OpenAPI 3, then press Convert. When the conversion has finished, press Close.
7. 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

```

 ![Screen Shot 2020-06-20 at 10.54.45](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/2X/8/8e6c11fa852ab4e7e91b7ce728c7f8d4aa6943e1.png)

== EXPECTED RESULT ==  
No errors occur.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [June 23, 2020, 6:27am UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/17 "2020-06-23T06:27:57Z")

</div>

Hey @sendres,

We are working on fixing this. CC @shrijana.g. 🙂

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![shrijana.g](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/shrijana.g/32/605_2.png) [@shrijana.g](https://devforum.zoom.us/u/shrijana.g)\
**Post date:** [June 30, 2020, 11:46pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/18 "2020-06-30T23:46:16Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![sendres](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sendres/32/3793_2.png) [@sendres](https://devforum.zoom.us/u/sendres)\
**Post date:** [July 1, 2020, 3:26pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/19 "2020-07-01T15:26:44Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [July 6, 2020, 5:51pm UTC](https://devforum.zoom.us/t/issues-with-swagger/7027/20 "2020-07-06T17:51:38Z")

</div>

Hey @sendres,

Thank you for your feedback. Fixing our Open API spec is one of our priorities.

Thanks,  
Tommy

[Next page](https://devforum.zoom.us/t/issues-with-swagger/7027.md?page=2)
