# The Zoom API schema documentation sucks

**URL:** <https://devforum.zoom.us/t/the-zoom-api-schema-documentation-sucks/83867>\
**Category:** API and Webhooks\
**Created:** [February 28, 2023, 3:33pm UTC](https://devforum.zoom.us/t/the-zoom-api-schema-documentation-sucks/83867 "2023-02-28T15:33:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![nikhil2](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/nikhil2/32/36522_2.png) [@nikhil2](https://devforum.zoom.us/u/nikhil2)\
**Post date:** [February 28, 2023, 3:33pm UTC](https://devforum.zoom.us/t/the-zoom-api-schema-documentation-sucks/83867/1 "2023-02-28T15:33:39Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**  
`/users/me/meetings?type=live`

**Description**  
I just wasted a few hours trying to debug some internal logic, and it turned out that your schemas are wrong and don’t represent the return values of the endpoint listed above. I’ve had this issue before and am fed up enough with it to post this rant.

**Error?**  
Here’s the return value I got from the list my meetings endpoint:  
`{"page_size":30,"total_records":1,"next_page_token":"","meetings":[{"uuid":"UiXAeK7PSd29F7yj8E5Izw==","id":87861145172,"host_id":"v4Xy1yE1Rzul6MwNCxdFag","topic":"Nikhil Shinday's Zoom Meeting","type":1,"duration":2033796963,"created_at":"2023-02-28T15:02:12Z","join_url":"https://us06web.zoom.us/j/87861145172?pwd=SmM3d0JFLzlWd2ljeXBKK2p3aHc0UT09"}]}`  
`page_number` and `page_count` are completely missing from this response. There’s no indication from the API documentation or the associated JSON schema linked in docs that these should be missing. I verified that both the documentation and the public JSON schema don’t reflect this. It’s clear that Zoom is trying to focus on becoming a platform, and that part of your strategy in doing so is to build a developer community. Things like this make the DX awful and make me want to stay away from your API with a yard stick.

**How To Reproduce**  
Used a Bearer token issued from Zoom’s OAuth endpoint to call the list meetings endpoint:  
`curl -XGET https://api.zoom.us/v2/users/me/meetings\?type\=live -H 'Authorization: Bearer <token>'`

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [February 28, 2023, 7:57pm UTC](https://devforum.zoom.us/t/the-zoom-api-schema-documentation-sucks/83867/2 "2023-02-28T19:57:39Z")

</div>

Hi @nikhil2  
Thank you so much for reaching out to us and for bringing this to our attention.  
I really appreciate your feedback and understand how this can be a bad user experience.  
We are currently working on improving our Docs site and I will make sure to pass along your feedback to our Docs team.

I did some testing on my end with this endpoint, and it looks like you need to pass the query parameters page\_number and page\_size in your request, so you will get a page\_number and page\_count field back in your response.

For example:

 ![Screenshot 2023-02-28 at 3.05.45 PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/8/0/805ce6eba0b166af583a8529f9d714b6fc5234ba.png)

Now, if you do not pass those query\_params, you will be getting a next\_page\_token back in your response, which will be used to paginate through the response you get.

 ![Screenshot 2023-02-28 at 3.09.43 PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/3/630f151bff7df5bfebc2e816b22faa9476008c38.png)

Let me know if this helps  
Thanks again,  
Elisa

---

<div class="post-metadata">

**Author:** ![4123958](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/4123958/32/45950_2.png) [@4123958](https://devforum.zoom.us/u/4123958)\
**Post date:** [February 28, 2023, 8:37pm UTC](https://devforum.zoom.us/t/the-zoom-api-schema-documentation-sucks/83867/3 "2023-02-28T20:37:03Z")

</div>

hi i have a need quick question

---

<div class="post-metadata">

**Author:** ![nikhil2](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/nikhil2/32/36522_2.png) [@nikhil2](https://devforum.zoom.us/u/nikhil2)\
**Post date:** [March 1, 2023, 5:35pm UTC](https://devforum.zoom.us/t/the-zoom-api-schema-documentation-sucks/83867/4 "2023-03-01T17:35:49Z")

</div>

> [@elisa.zoom](#):
>
> ![Screenshot 2023-02-28 at 3.05.45 PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/8/0/805ce6eba0b166af583a8529f9d714b6fc5234ba.png)

Thanks for your response, Elisa. I checked the Pagination page and the Meeting List endpoint on the docs and neither mentions this. Appreciate the clarification and also _really_ think that should be mentioned somewhere.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [March 1, 2023, 7:11pm UTC](https://devforum.zoom.us/t/the-zoom-api-schema-documentation-sucks/83867/5 "2023-03-01T19:11:44Z")

</div>

I totally understand you @nikhil2 and will reach out to our Docs team to add a clarification note.  
Thanks again 🙂  
Cheers,  
Elisa

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [March 4, 2024, 10:48am UTC](https://devforum.zoom.us/t/the-zoom-api-schema-documentation-sucks/83867/6 "2024-03-04T10:48:16Z")

</div>

Closed on March 4, 2024, 10:48am UTC

This topic was automatically closed 368 days after the last reply. New replies are no longer allowed.
