# Next Page Token Issue

**URL:** <https://devforum.zoom.us/t/next-page-token-issue/93775>\
**Category:** Meetings\
**Tags:** api\
**Created:** [August 22, 2023, 1:14pm UTC](https://devforum.zoom.us/t/next-page-token-issue/93775 "2023-08-22T13:14:47Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [August 24, 2023, 8:14pm UTC](https://devforum.zoom.us/t/next-page-token-issue/93775/4 "2023-08-24T20:14:10Z")

</div>

Interesting, @jeffblackwood86  
Here is a helpful post on how to handle next\_page\_token with recursion

> [@Handling paginated responses from the Zoom API](https://devforum.zoom.us/t/handling-paginated-responses-from-the-zoom-api/68825):
>
> When an API response contains more data than can be returned in a single page, the API will return with a token to request the next page of results. But how will you expect to receive a paginated response? If your response contains a next page token, make the same request again using that token as a query parameter. Say you have 70 users on your account, as in, more than the default page size of 30. A request to the list users will initially respond with 30 users. To get the full list, you’ll …

I will also go ahead and send you a private message to get more details about your specific case  
Cheers,  
Elisa

---

_[View the full topic](https://devforum.zoom.us/t/next-page-token-issue/93775)._
