# Sever to server Oauth page size 300

**URL:** <https://devforum.zoom.us/t/sever-to-server-oauth-page-size-300/96589>\
**Category:** Webinars\
**Tags:** s2s-oauth\
**Created:** [October 11, 2023, 10:05am UTC](https://devforum.zoom.us/t/sever-to-server-oauth-page-size-300/96589 "2023-10-11T10:05:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mlh](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/mlh/32/52906_2.png) [@mlh](https://devforum.zoom.us/u/mlh)\
**Post date:** [October 11, 2023, 10:05am UTC](https://devforum.zoom.us/t/sever-to-server-oauth-page-size-300/96589/1 "2023-10-11T10:05:29Z")

</div>

We are trying to integrate server to server oauth. When we are fetching all attendee data showing maximum 300 page size only. how we can increase page size?

Second there is no clarity for next page data using curl php.  
While create server to server we are getting server (retires in October) what does that mean?

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [October 11, 2023, 11:57am UTC](https://devforum.zoom.us/t/sever-to-server-oauth-page-size-300/96589/2 "2023-10-11T11:57:54Z")

</div>

@mlh,

Have you tried to paginate the response to get the full list?

Here is a helpful forum post on that :

> [@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 …

> [@mlh](#):
>
> Second there is no clarity for next page data using curl php.  
> While create server to server we are getting server (retires in October) what does that mean?

Please provide more details about the issue you are facing regarding the lack of clarity for retrieving next page data using cURL in PHP. Can you explain what you have already tried and what the resulting outcome was? If possible, please share a code snippet that I can test on my end. Additionally, it would be helpful if you could provide a screenshot of the response you are receiving from the server.