We’ve been using the /v2/phone/users endpoint for several years without issues. However, starting on May 19th between 1:04–1:34 PM, we began noticing duplicate user records in the response.
We paginate through the results using the next_page_token and request 100 records at a time using the page_size parameter. Despite this, the total number of users returned after paginating through all pages does not match the total_records value in the response. Some users appear as duplicates one day and are completely missing the next, which is causing our production process to fail due to inconsistent and unreliable data.
I have also tried testing the endpoint with different page_size parameters. Yesterday 5/21, we pulled back 915 users with a page_size of 100. Today it’s returning 614. If I change the page_size to 300 it returns 911 users, page_size=200 returns 2615 records. Total_Records in the response is 2901.
Although the endpoint isn’t throwing any errors, the integrity of the data has changed. This issue began during a time that aligns with recent Zoom platform updates listed in the changelog, though none specifically mention changes to the /phone/users endpoint.
We’ve attempted to open support tickets but have been redirected here.
I am also having this issue that started around the same time you have mentioned. I tried to open up a support case, but they responded with this.
Hello,
Our Technical Support team assists with product-level defects. We have confirmed this issue is configuration-related and not within the scope of your account’s Developer Support Plan, as such this case will be closed.
For help with developer configuration issues, custom solutions, custom integrations, or feature requests, please visit our Developer Forum where Zoom Developers and community members are available to assist you.
This is not very helpful Zoom! This is NOT a configuration issue on my end but rather your end and you need to fix this issue!
From what I have seen in some testing is that the “next_page_token” is blank on some request responses when it should not be. Resulting in not being able to get all phone users.
After running a bunch of tests, it looks like this issue has been resolved. I’m able to consistently get my full list of users without duplicates or missing users.
Hi @dlavine and @erikc
Sorry to hear to are having this issues and that your support ticket was closed.
I am happy to take a closer look into this issue.
I will DM @dlavine to get some additional data to share with our Engineering team.