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