# API v1 vs v2 List Users

**URL:** <https://devforum.zoom.us/t/api-v1-vs-v2-list-users/978>\
**Category:** API and Webhooks\
**Created:** [February 15, 2018, 9:48pm UTC](https://devforum.zoom.us/t/api-v1-vs-v2-list-users/978 "2018-02-15T21:48:22Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Almonrode](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/david_almonrode/32/64_2.png) [@David\_Almonrode](https://devforum.zoom.us/u/David_Almonrode)\
**Post date:** [February 15, 2018, 9:48pm UTC](https://devforum.zoom.us/t/api-v1-vs-v2-list-users/978/1 "2018-02-15T21:48:22Z")

</div>

With v1 of the API, I’m use /user/list to get all of my users and their licenses/features.

This takes about 200 API calls with a page size of 300, my current job takes 2-4 minutes, and syncs the data local (SQL) and to our Service Now instance.

With v2 of the API, it seems I have to uses /users to retrieve their IDs and then /settings for each id. For me, this adds over 60,000 additional API calls and is taking hours to complete.

Am I missing an endpoint that would better fit my needs?

&nbsp;

I would be helpful to have a query syntax so I could retrieve only/all the data I need in a single call.

?webinar=true?webinar\_capacity=1000?large\_meeting=true

---

<div class="post-metadata">

**Author:** ![Zoom\_Developer](https://avatars.discourse-cdn.com/v4/letter/z/eb8c5e/32.png) [@Zoom\_Developer](https://devforum.zoom.us/u/Zoom_Developer)\
**Post date:** [February 16, 2018, 12:36am UTC](https://devforum.zoom.us/t/api-v1-vs-v2-list-users/978/2 "2018-02-16T00:36:59Z")

</div>

Hi David, we will add this in the next release in April. should be useful for everyone.&nbsp;

&nbsp;

Wei

---

<div class="post-metadata">

**Author:** ![David\_Almonrode](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/david_almonrode/32/64_2.png) [@David\_Almonrode](https://devforum.zoom.us/u/David_Almonrode)\
**Post date:** [February 16, 2018, 1:08pm UTC](https://devforum.zoom.us/t/api-v1-vs-v2-list-users/978/3 "2018-02-16T13:08:00Z")

</div>

You believe this will cover my use case? Will it offer a new query based endpoint or allow joining of multiple existing ones?

---

<div class="post-metadata">

**Author:** ![Matt\_Rogers](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/matt_rogers/32/189_2.png) [@Matt\_Rogers](https://devforum.zoom.us/u/Matt_Rogers)\
**Post date:** [July 28, 2018, 12:36am UTC](https://devforum.zoom.us/t/api-v1-vs-v2-list-users/978/4 "2018-07-28T00:36:47Z")

</div>

Unrelated to your question, but how are you dealing with pagination on the /users endpoint?&nbsp; I am not getting a next\_page\_token back, and post/get with a new page number returns the same results every time.&nbsp;&nbsp;

On the /metrics endpoint, a next\_page\_token is returned.

Am I missing&nbsp;something obvious here?

---

<div class="post-metadata">

**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\
**Post date:** [July 30, 2018, 9:20pm UTC](https://devforum.zoom.us/t/api-v1-vs-v2-list-users/978/5 "2018-07-30T21:20:56Z")

</div>

Hi Matt,&nbsp;

For the users endpoint, you can use the page\_number parameter. The number of pages is determined based on the numbers you have on your account.&nbsp;

Thanks

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 5:48pm UTC](https://devforum.zoom.us/t/api-v1-vs-v2-list-users/978/6 "2020-08-21T17:48:31Z")

</div>

Closed on August 21, 2020, 5:48pm UTC