# List group members API docs misleading

**URL:** <https://devforum.zoom.us/t/list-group-members-api-docs-misleading/32246>\
**Category:** API and Webhooks\
**Created:** [October 5, 2020, 8:54pm UTC](https://devforum.zoom.us/t/list-group-members-api-docs-misleading/32246 "2020-10-05T20:54:03Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![garrett](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/garrett/32/13346_2.png) [@garrett](https://devforum.zoom.us/u/garrett)\
**Post date:** [October 5, 2020, 8:54pm UTC](https://devforum.zoom.us/t/list-group-members-api-docs-misleading/32246/1 "2020-10-05T20:54:03Z")

</div>

**Description**  
The documentation for the “list group members” api ( [https://marketplace.zoom.us/docs/api-reference/zoom-api/groups/groupmembers](https://marketplace.zoom.us/docs/api-reference/zoom-api/groups/groupmembers) ) states of the “page\_number” query parameter ‘This field has been deprecated and we will stop supporting it completely in a future release. Please use “next\_page\_token” for pagination instead of this field.’ However the response doesn’t actually include the “next\_page\_token.” As far as I can tell it isn’t possible to follow the recommendation provided by the documentation. This note should be removed from the documentation until the API has been updated to accept / return the recommended value.

**Error**  
N/A

**Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
N/A

**Which Endpoint/s?**  
get /groups/{groupId}/members

**How To Reproduce (If applicable)**  
N/A

**Screenshots (If applicable)**  
N/A

**Additional context**  
N/A

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [October 6, 2020, 5:37pm UTC](https://devforum.zoom.us/t/list-group-members-api-docs-misleading/32246/2 "2020-10-06T17:37:45Z")

</div>

Hey @garrett,

Thanks for raising this. Is it possible to share your full request with me so that I can take a closer look? The set of available results will need to exceed that of the current page in order for the `next_page_token` to be returned. Are you including a `page_size` parameter in your request?

Let me know—thanks!  
Will

---

<div class="post-metadata">

**Author:** ![garrett](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/garrett/32/13346_2.png) [@garrett](https://devforum.zoom.us/u/garrett)\
**Post date:** [October 6, 2020, 5:56pm UTC](https://devforum.zoom.us/t/list-group-members-api-docs-misleading/32246/3 "2020-10-06T17:56:48Z")

</div>

Hi Will,  
See the example below. The group I’m querying is our default user group with about 6000 members. with page\_size set to the maximum of 300 it returns the first 300 objects and a page number, but no next\_page\_token. The response included page\_count, page\_number, page\_size, total\_records, and the array of the first 300 members. In order to query the remaining pages i had to use the page\_number parameter in my request that it says is deprecated.

```
[13:50:50]:C:\Scripts\PowerShell\zoom> $body

Name Value
---- -----
page_size 300

[13:51:08]:C:\Scripts\PowerShell\zoom> $groupMemberUri

https://api.zoom.us/v2/groups/<myRedactedGroupIdHere>/members
[13:51:10]:C:\Scripts\PowerShell\zoom> $headers

Name Value
---- -----
Authorization Bearer <redacted jwt>

[13:51:14]:C:\Scripts\PowerShell\zoom> $results = Invoke-RestMethod -Uri $groupMemberUri -Headers $headers -Body $body

[13:51:39]:C:\Scripts\PowerShell\zoom> $results

page_count : 22
page_number : 1
page_size : 300
total_records : 6325
members : {<array of members here - redacted}
```

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [October 7, 2020, 5:52pm UTC](https://devforum.zoom.us/t/list-group-members-api-docs-misleading/32246/4 "2020-10-07T17:52:26Z")

</div>

Hey @garrett,

Thanks for sharing this. Our team is looking into this (ZOOM-204204).

I’ll follow up here once I have an update!

Thanks,  
Will

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [October 12, 2020, 1:11pm UTC](https://devforum.zoom.us/t/list-group-members-api-docs-misleading/32246/5 "2020-10-12T13:11:19Z")

</div>

Hey @garrett,

I heard back from my team on this, and they’ve let me know that the `next_page_token` parameter will be released shortly, but you will want to continue to use the `next_page` parameter for the very short term. We expect this to be fixed very soon.

Thanks,  
Will

---

<div class="post-metadata">

**Author:** ![garrett](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/garrett/32/13346_2.png) [@garrett](https://devforum.zoom.us/u/garrett)\
**Post date:** [October 12, 2020, 1:54pm UTC](https://devforum.zoom.us/t/list-group-members-api-docs-misleading/32246/6 "2020-10-12T13:54:42Z")

</div>

Sounds good Will, thanks for the update!

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [October 13, 2020, 4:50pm UTC](https://devforum.zoom.us/t/list-group-members-api-docs-misleading/32246/7 "2020-10-13T16:50:57Z")

</div>

@garrett of course, thanks for raising it!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [November 13, 2020, 2:50am UTC](https://devforum.zoom.us/t/list-group-members-api-docs-misleading/32246/8 "2020-11-13T02:50:59Z")

</div>

Closed on November 13, 2020, 2:50am UTC

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