/v2/users returns inconsistent data when page_number is used

When page_number is appended to the API call for api.zoom.us/v2/users/, it returns data that is wildly inconsistent and sometimes incorrect

When I call https://api.zoom.us/v2/users?access_token=xxx&page_size=300 the results returned are accurate and match those from the admin web UI. However, when I go to the next page via https://api.zoom.us/v2/users?access_token=xxx&page_size=300&page_number=2 the results are random and many times repeats users from the first page. This seems to happen with any API call where the page number is used.

I read where pagination will be the new standard, but it’s not available on the calls I’m making. For example, when I call https://api.zoom.us/v2/users?access_token=xxx&page_size=300 I get returned:


There is no next_page_token available to get.

This issue is causing my reports to be totally unusable. Please advise.

Which App Type (OAuth / Chatbot / JWT / Webhook)?

Which Endpoint/s?

How To Reproduce (If applicable)
Call the API with data that has more than 300 users and look at the second page

Screenshots (If applicable)

Additional context

Hey @adam.frost,

Thank you for reaching out to the Zoom Developer Forum. It’s possible that this is at least partially related to an ongoing issue that we have (ZOOM-221082). In order for us to investigate this further, please send an email to developersupport@zoom.us with a link to this thread as well as steps for us to reproduce the issue.


Thanks Max. I have opened a ticket with the dev group (#9079971).

I don’t know where to find the ZOOM-221082 issue. Is it a public ticket that I can view? I’d like to know what it generally says so I can report back to my boss.

Hey @adam.frost,

Thank you for the update. I took ownership of the ticket that you’ve submitted and will be sure to follow up there. In regard to the issue ZOOM-221082, that is an internal tag that I can use to locate any related threads. I’ll provide more information on our ticket.


Hey all,

I wanted to update this forum post with the solution that we found in our ticket in the event that it is helpful for others that find this thread. We found that when requesting an XML response instead of JSON, the next_page_token will not be returned. The best practice here is to make sure that you are requesting a Content-Type of application/json and that instead of using page_number, the next_page_token is used in subsequent requests.

I hope that helps!


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