# api.zoom.us/v2/users/{userId}/meetings API not returning all possible results

**URL:** <https://devforum.zoom.us/t/api-zoom-us-v2-users-userid-meetings-api-not-returning-all-possible-results/134390>\
**Category:** Meetings\
**Created:** [June 24, 2025, 9:18am UTC](https://devforum.zoom.us/t/api-zoom-us-v2-users-userid-meetings-api-not-returning-all-possible-results/134390 "2025-06-24T09:18:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Troy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/troy/32/69849_2.png) [@Troy](https://devforum.zoom.us/u/Troy)\
**Post date:** [June 24, 2025, 9:18am UTC](https://devforum.zoom.us/t/api-zoom-us-v2-users-userid-meetings-api-not-returning-all-possible-results/134390/1 "2025-06-24T09:18:46Z")

</div>

In relation to the  
get /users/{userId}/meetings

I’m facing an issue where this API fails to return all possible results. An example of this is I can manually verify that a user has more than one meeting in a day, under separate meeting ID’s, however the API only returns 1 result. This behaviour is random as requesting meetings for a different user will return all the meetings successfully. What does seem consistent, but I can’t fully confirm is that certain meeting ID’s are never returned for a user - however if I manually get the ID and retrieve recordings using the appropriate API endpoint, I can do so successfully.

I have tried everything I can think of and extensively searched for a solution with no joy - any thoughts would be appreciated.

I am using the following URL parameters:  
type: previous\_meetings  
from: (code generated date/time)  
to: (code generated date/time)  
timezone: UTC  
page\_size: 300

---

<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:** [June 27, 2025, 1:34pm UTC](https://devforum.zoom.us/t/api-zoom-us-v2-users-userid-meetings-api-not-returning-all-possible-results/134390/2 "2025-06-27T13:34:20Z")

</div>

Hi @Troy  
Thanks for reaching out to us and welcome to the Zoom Developer Forum!  
I am happy to help here! Can you please confirm if you are trying to get only past meetings?  
Have you tried using our Report endpoint to confirm if this is happening too:

> **[Meetings APIs](https://developers.zoom.us/docs/api/meetings/#tag/reports/GET/report/users/%7BuserId%7D/meetings)**
>
> The Zoom Meeting APIs allow developers to interface with Zoom Meetings and Webinars programmatically.

---

<div class="post-metadata">

**Author:** ![Troy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/troy/32/69849_2.png) [@Troy](https://devforum.zoom.us/u/Troy)\
**Post date:** [June 27, 2025, 1:53pm UTC](https://devforum.zoom.us/t/api-zoom-us-v2-users-userid-meetings-api-not-returning-all-possible-results/134390/3 "2025-06-27T13:53:55Z")

</div>

Hi Elisa,

Thanks for your reply. I am having this issue with this endpoint set to both past meetings and when set to scheduled.

I haven’t tried using the report endpoint as of yet, but I can manually try this and see if it consistently reports the missing ID’s.

---

<div class="post-metadata">

**Author:** ![David32](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/david32/32/51565_2.png) [@David32](https://devforum.zoom.us/u/David32)\
**Post date:** [July 17, 2025, 8:28am UTC](https://devforum.zoom.us/t/api-zoom-us-v2-users-userid-meetings-api-not-returning-all-possible-results/134390/4 "2025-07-17T08:28:08Z")

</div>

just a quick note. this end point won’t return **instant** meetings.

---

<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:** [July 17, 2025, 4:13pm UTC](https://devforum.zoom.us/t/api-zoom-us-v2-users-userid-meetings-api-not-returning-all-possible-results/134390/5 "2025-07-17T16:13:47Z")

</div>

Hey @Troy  
Sorry I did not reply sooner, I did not receive a notification about this.  
Are you still having this issue?
