# \[BUG\] Zoom Event List Registrants API

**URL:** <https://devforum.zoom.us/t/bug-zoom-event-list-registrants-api/125095>\
**Category:** API and Webhooks\
**Tags:** api\
**Created:** [January 22, 2025, 7:46pm UTC](https://devforum.zoom.us/t/bug-zoom-event-list-registrants-api/125095 "2025-01-22T19:46:18Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![rhuamanicarpio](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rhuamanicarpio/32/63618_2.png) [@rhuamanicarpio](https://devforum.zoom.us/u/rhuamanicarpio)\
**Post date:** [January 22, 2025, 7:46pm UTC](https://devforum.zoom.us/t/bug-zoom-event-list-registrants-api/125095/1 "2025-01-22T19:46:18Z")

</div>

Hello. I’ve previously worked with Zoom Meeting and Zoom Webinar APIs.

They both have a “list registrants” API where a page size can be specified to specify how many records need to be returned.

the response has “total\_records” which is how many records are total. We currently call this with page\_size=1 and we don’t actually need to use the actual records, we just want to know how many there are (which total\_records returns.) Zoom Events has the same API.

however when testing, this List Registrants API for Zoom Events doesn’t work as expected. if i specify page\_size=1, i get one record (expected) but total\_records=1 (which is not the actual number of records there are). If i specify any other number \>0 the same thing is returned. However, when I specify page\_size=0, that’s when total\_records actually reflects the correct number. However, it returns all records.

This looks like a bug and if not what’s the best way to get the number of total number of registrants?

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [January 27, 2025, 8:53pm UTC](https://devforum.zoom.us/t/bug-zoom-event-list-registrants-api/125095/2 "2025-01-27T20:53:41Z")

</div>

Hi @rhuamanicarpio  
Thanks for reaching out to us.  
Allow me to do some testing on my end and identify a root cause.

---

<div class="post-metadata">

**Author:** ![rhuamanicarpio](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rhuamanicarpio/32/63618_2.png) [@rhuamanicarpio](https://devforum.zoom.us/u/rhuamanicarpio)\
**Post date:** [April 24, 2025, 5:18pm UTC](https://devforum.zoom.us/t/bug-zoom-event-list-registrants-api/125095/3 "2025-04-24T17:18:25Z")

</div>

Hi Elisa! Is there an update on this? It’s giving us issues in production as total\_records is not returning the correct value for the Zoom Event Registrants API

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [April 24, 2025, 7:51pm UTC](https://devforum.zoom.us/t/bug-zoom-event-list-registrants-api/125095/4 "2025-04-24T19:51:09Z")

</div>

Hey @rhuamanicarpio  
Can you please share an example request URL and response body please?

---

<div class="post-metadata">

**Author:** ![rhuamanicarpio](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rhuamanicarpio/32/63618_2.png) [@rhuamanicarpio](https://devforum.zoom.us/u/rhuamanicarpio)\
**Post date:** [April 24, 2025, 8:04pm UTC](https://devforum.zoom.us/t/bug-zoom-event-list-registrants-api/125095/5 "2025-04-24T20:04:06Z")

</div>

v2/zoom\_events/events/lFuJPgBJTrOU3lJqssBK9A/registrants?page\_size=0

response body looks like  
"{  
“total\_records”: 30,  
"  
}  
when there are more than 30 total records. it seems to cap at 30.

we used page\_size=0 as a workaround because using page\_size=X returns total\_records=X always. it is our understanding that the API should be returning the actual total records in the total\_records field despite what page size is.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [April 24, 2025, 8:11pm UTC](https://devforum.zoom.us/t/bug-zoom-event-list-registrants-api/125095/6 "2025-04-24T20:11:25Z")

</div>

Can you pass a page\_size of 300 please?

---

<div class="post-metadata">

**Author:** ![rhuamanicarpio](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rhuamanicarpio/32/63618_2.png) [@rhuamanicarpio](https://devforum.zoom.us/u/rhuamanicarpio)\
**Post date:** [April 24, 2025, 8:23pm UTC](https://devforum.zoom.us/t/bug-zoom-event-list-registrants-api/125095/7 "2025-04-24T20:23:03Z")

</div>

hi Elisa that works but is the API supposed to return the actual total\_records in that field despite page size? we dont actually need to fetch all the records individually we just care about the number. we do this with meetings and webinars API so this behavior seems inconsistent.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [April 25, 2025, 12:44pm UTC](https://devforum.zoom.us/t/bug-zoom-event-list-registrants-api/125095/8 "2025-04-25T12:44:21Z")

</div>

Hi @rhuamanicarpio  
Yes, the endpoint will return all records associated with the event. I will double check with the team if this is a bug as you mentioned in the original post, but for now I suggest you set the page\_size to 300 so you get all records back

---

<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:** [April 28, 2025, 4:41pm UTC](https://devforum.zoom.us/t/bug-zoom-event-list-registrants-api/125095/9 "2025-04-28T16:41:54Z")

</div>

Closed on April 28, 2025, 4:41pm UTC

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