# Upcoming meetings API returns an empty response

**URL:** <https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937>\
**Category:** API and Webhooks\
**Tags:** api\
**Created:** [August 27, 2026, 10:14am UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937 "2026-08-27T10:14:26Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![androiddev123](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/androiddev123/32/76094_2.png) [@androiddev123](https://devforum.zoom.us/u/androiddev123)\
**Post date:** [August 27, 2026, 10:14am UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/1 "2026-08-27T10:14:26Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**

```auto
https://api.zoom.us/v2/users/me/upcoming_meetings

```

\*\*Description\*\*  
_The upcoming meetings API returns an empty response for some accounts, even though there are meetings scheduled on the zoom website. This behavior is very flaky, as it only happens for some of the accounts I’ve tested this with and works fine for the rest._

**Error?**  
_The response for the upcoming meetings API is an empty JSON object._

`{}` ← this is the response

**How To Reproduce**  
_Steps to reproduce the behavior:_  
_This issue only seems to happen for some accounts, and hence the reproducibility is not guaranteed. But to try, the following steps can be performed_

1. Acquire an access token by going through any appropriate authentication flow. We used the device code flow.
2. Schedule a few meetings on your Zoom account.
3. Use the access code form the previous step to make a request to the API linked above.
4. Observe the response.

---

<div class="post-metadata">

**Author:** ![MultiplayerSession](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/multiplayersession/32/66446_2.png) [@MultiplayerSession](https://devforum.zoom.us/u/MultiplayerSession)\
**Post date:** [August 27, 2026, 2:50pm UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/2 "2026-08-27T14:50:40Z")

</div>

How distant are the upcoming meetings? [List upcoming meetings](https://developers.zoom.us/docs/api/meetings/#tag/meetings/get/users/%7BuserId%7D/upcoming_meetings) is documented with a time range of 24 hours, while [List meetings](https://developers.zoom.us/docs/api/meetings/#tag/meetings/get/users/%7BuserId%7D/meetings) with a directional type​ is documented with a time range of 6 months.

---

<div class="post-metadata">

**Author:** ![androiddev123](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/androiddev123/32/76094_2.png) [@androiddev123](https://devforum.zoom.us/u/androiddev123)\
**Post date:** [August 29, 2026, 7:54am UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/3 "2026-08-29T07:54:26Z")

</div>

All the meetings that we are expecting to see are scheduled withing 24hrs of when the API call was made. Also, even when there are no meetings scheduled within the next 24hrs, the expected response from the API contains an empty meetings list and a total\_records field set to 0. LIke this:

```json
{
  "total_records": 0,
  "meetings": []
}

```

But what we receive is:

`{}`

---

<div class="post-metadata">

**Author:** ![androiddev123](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/androiddev123/32/76094_2.png) [@androiddev123](https://devforum.zoom.us/u/androiddev123)\
**Post date:** [September 1, 2026, 7:06am UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/4 "2026-09-01T07:06:29Z")

</div>

hey @MultiplayerSession,  
are there any updates on this?

---

<div class="post-metadata">

**Author:** ![MultiplayerSession](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/multiplayersession/32/66446_2.png) [@MultiplayerSession](https://devforum.zoom.us/u/MultiplayerSession)\
**Post date:** [September 1, 2026, 9:35pm UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/5 "2026-09-01T21:35:16Z")

</div>

Definitely seems like undocumented behavior. Is the HTTP response code 200 (some programming frameworks make it easy to ignore failure HTTP response codes); are there any unusual response headers that might imply something else is interfering with the response (I think the Zoom APIs route through Cloudflare)? Have you checked the [API Call Logs](https://marketplace.zoom.us/user/logs) for additional insights?

---

<div class="post-metadata">

**Author:** ![Manager2](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/manager2/32/76407_2.png) [@Manager2](https://devforum.zoom.us/u/Manager2)\
**Post date:** [September 2, 2026, 12:31pm UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/6 "2026-09-02T12:31:08Z")

</div>

great answer boro and i was also dealing with the same problem so this ans helped me in solving my own issue. so once again I am really thankful to you 👏🏻

---

<div class="post-metadata">

**Author:** ![Andrew29](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/andrew29/32/50330_2.png) [@Andrew29](https://devforum.zoom.us/u/Andrew29)\
**Post date:** [September 3, 2026, 2:54am UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/7 "2026-09-03T02:54:39Z")

</div>

Hi,

This issue may be related to account permissions, authentication scope, or the way upcoming meetings are being queried. I would first verify that the access token has the required scopes (such as `meeting:read` / `meeting:read:admin`) and that the user ID in the endpoint is correct.

Also, try testing with `/users/{userId}/upcoming_meetings` instead of `/users/me/upcoming_meetings` to confirm whether it is an account-specific issue. Checking the API response headers and trying a fresh token may also help identify the cause.

---

<div class="post-metadata">

**Author:** ![Hammer](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/hammer/32/76082_2.png) [@Hammer](https://devforum.zoom.us/u/Hammer)\
**Post date:** [September 10, 2026, 3:25am UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/8 "2026-09-10T03:25:38Z")

</div>

I have the exact same issue and have not yet found a solution to this. Infuriating.

---

<div class="post-metadata">

**Author:** ![androiddev123](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/androiddev123/32/76094_2.png) [@androiddev123](https://devforum.zoom.us/u/androiddev123)\
**Post date:** [September 16, 2026, 12:28pm UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/9 "2026-09-16T12:28:04Z")

</div>

Hi @MultiplayerSession ,

Thanks for replying. I have checked the API logs as well but there wasn’t anything that indicated what the error was. This is what the API logs page shows.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/2/62e1323cc4fb3ed09510c809cf5de86713df642f.png)

As you can see the response here is empty. I can confirm that there is indeed an upcoming meeting scheduled as can be seen in the screenshot below.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/7/9/79816d797d2958a2b6a39833e6c817c1d08122df.png)

This issue is a blocker and we are not able to proceed with our app due to this. Please help us get a resolution for this issue.

Thanks

cc: @chunsiong.zoom

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [September 16, 2026, 3:53pm UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/10 "2026-09-16T15:53:49Z")

</div>

> [@androiddev123](#):
>
> As you can see the response here is empty. I can confirm that there is indeed an upcoming meeting scheduled as can be seen in the screenshot below.
> 
> ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/7/9/79816d797d2958a2b6a39833e6c817c1d08122df.png)
> 
> This issue is a blocker and we are not able to proceed with our app due to this. Please help us get a resolution for this issue.
> 
> Thanks

Hi @androiddev123 confirming that you are trying to see your own meetings and not another user’s meetings on the same Zoom account? If you are looking for your own meetings {me} is fine. If looking for another internal user’s meetings who you have permission and scope to view their meetings, use their {email} or {userId}.

If it is your own meetings you’re looking for and still not able to see with {me} could you please try with your {email} like @Andrew29 suggested?

If you still cannot see your upcoming meetings with either {me} or your {email} despite correct scopes, please open a BUG ticket: [New Request](https://support.zoom.com/hc/en/new-request?id=new_request&sys_id=7a69170f87cee15089a37408dabb3591&product=developer&ampDeviceId=dd392f4c-243a-4e7f-9a5e-3502830bbf5d&ampSessionId=1789572398366&%5C_ics=1789573865367&irclickid=%5C~275%5C~7X3VYSRJKGIHKLBIzpqwqkpqkifbhdahi%5C~-874UJGywpomja&%5C_gl=1%5C*j3ld3w%5C*%5C_gcl_au%5C*MTg3ODA2MTIzOS4xNzg5NTcyNTM4%5C*%5C_ga%5C*ODY4NTY2MTU5LjE3NjYwMDMwNDc.%5C*%5C_ga_L8TBF28DDX%5C*czE3ODk1NzIzOTAkbzExNyRnMSR0MTc4OTU3Mzg2MyRqNTYkbDAkaDA) .

Include your app’s clientId, zm-tracking-id from the response headers, a description of the behavior, link to this post saying a Developer Advocate asked you to open a bug ticket.

Talk soon!

---

<div class="post-metadata">

**Author:** ![androiddev123](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/androiddev123/32/76094_2.png) [@androiddev123](https://devforum.zoom.us/u/androiddev123)\
**Post date:** [September 18, 2026, 6:27am UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/12 "2026-09-18T06:27:40Z")

</div>

hi @gianni.zoom

thanks for replying. yes, i am trying to view meetings in my own account (i.e. the account that i got the access token for after signing in via the device code flow). i tried replacing `me` with the user’s `email` but still got an empty response for upcoming meetings i.e. `{}`.

i clicked on the ‘New Request’ link that you shared in the previous response but could not see any option to open a BUG ticket, as can be seen in the screenshot below.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/3/4/34470eae10469860c439fee7bf3755ed8eb1b004.png)

oh also @gianni.zoom,

this problem seems to only happen with the `upcoming_meetings` API ([Meetings APIs - API - Zoom Developer Docs](https://developers.zoom.us/docs/api/meetings/#tag/meetings/get/users/%7BuserId%7D/upcoming_meetings)). If I use the `list meetings` API ([Meetings APIs - API - Zoom Developer Docs](https://developers.zoom.us/docs/api/meetings/#tag/meetings/get/users/%7BuserId%7D/meetings)) instead then that one returns the meetings correctly, even the upcoming ones.

but this one returns all the meetings, not just the upcoming\_meetings. for our requirement we only need the upcoming\_meetings API.

---

<div class="post-metadata">

**Author:** ![freecine](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/freecine/32/76716_2.png) [@freecine](https://devforum.zoom.us/u/freecine)\
**Post date:** [September 19, 2026, 10:27am UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/13 "2026-09-19T10:27:26Z")

</div>

The Zoom Upcoming Meetings API may return an empty response when the authenticated user has no upcoming meetings or the request lacks the required permissions.

---

<div class="post-metadata">

**Author:** ![androiddev123](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/androiddev123/32/76094_2.png) [@androiddev123](https://devforum.zoom.us/u/androiddev123)\
**Post date:** [September 21, 2026, 5:05am UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/14 "2026-09-21T05:05:19Z")

</div>

the user does indeed have upcoming meetings scheduled (within the next 24hrs). this was confirmed from the response coming from the scheduled meetings API (mentioned in my previous response in this thread) and is also visible on Zoom’s own website.

the access token passed in the response also contains the required permissions since this same flow works for some accounts while does not for others. we can confirm that the user accepts all required permissions when signing into the app.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/9/8/984919ac10453f099137d20810dac6eb02ac32d6.png)

cc: @gianni.zoom @chunsiong.zoom

---

<div class="post-metadata">

**Author:** ![androiddev123](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/androiddev123/32/76094_2.png) [@androiddev123](https://devforum.zoom.us/u/androiddev123)\
**Post date:** [September 22, 2026, 5:27am UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/15 "2026-09-22T05:27:03Z")

</div>

hi @gianni.zoom

thanks for responding to the earlier message. as metioned we arent able to open a bug ticket and have tried every other solution mentioned in this thread but couldnt get the upcoming meetings endpoint to work as expected. could you let us know further steps we need to take as its causing a delay in our development process

regards

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [September 22, 2026, 2:15pm UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/16 "2026-09-22T14:15:29Z")

</div>

Hi @androiddev123 ,

> [@androiddev123](#):
>
> oh also @gianni.zoom,
> 
> this problem seems to only happen with the `upcoming_meetings` API ( [Meetings APIs - API - Zoom Developer Docs](https://developers.zoom.us/docs/api/meetings/#tag/meetings/get/users/%7BuserId%7D/upcoming_meetings) ). If I use the `list meetings` API ( [Meetings APIs - API - Zoom Developer Docs](https://developers.zoom.us/docs/api/meetings/#tag/meetings/get/users/%7BuserId%7D/meetings) ) instead then that one returns the meetings correctly, even the upcoming ones.
> 
> but this one returns all the meetings, not just the upcoming\_meetings. for our requirement we only need the upcoming\_meetings API.

Thank you for testing both endpoints and clarifying that you get the scheduled meetings within the next 24 hours for [List meetings](https://developers.zoom.us/docs/api/meetings/#tag/meetings/get/users/%7BuserId%7D/meetings), but not for [List upcoming meetings](https://developers.zoom.us/docs/api/meetings/#tag/meetings/get/users/%7BuserId%7D/upcoming_meetings) as expected.

For the **List meetings** endpoint, did you set the correct query parameter (see image below) that filters for only scheduled meetings?

 ![Screenshot 2026-09-22 at 10.02.15 AM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/2/9/29a49256f730ebf50fad7dd2a420e77d84c8b522.png)  
I will also ask the dev team why there is both `type:upcoming` and `type:upcoming_meetings` as they seem like unnecessary redundancies.

> [@androiddev123](#):
>
> thanks for replying. yes, i am trying to view meetings in my own account (i.e. the account that i got the access token for after signing in via the device code flow). i tried replacing `me` with the user’s `email` but still got an empty response for upcoming meetings i.e. `{}`.
> 
> i clicked on the ‘New Request’ link that you shared in the previous response but could not see any option to open a BUG ticket, as can be seen in the screenshot below.
> 
> ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/3/4/34470eae10469860c439fee7bf3755ed8eb1b004.png)

Ahh I see. I believe it used to be that you could submit support tickets for bugs even with a free plan, but I will double check with that team!

Please respond to my private message with the following: **Include your app’s clientId, zm-tracking-id from the response headers, a description of the behavior, link to this post saying a Developer Advocate asked you to open a bug ticket.**

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [October 2, 2026, 9:11pm UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/17 "2026-10-02T21:11:00Z")

</div>

We are investigating possible bug (ZSEE-215591), will share updates soon!

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [October 12, 2026, 5:18pm UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/18 "2026-10-12T17:18:33Z")

</div>

Hi @androiddev123 ,

The issue is not resolved yet and I have not received an updated timeline on the fix, but we have followed up today. Can you please use List meetings endpoint with `upcoming_meetings` parameter in the meantime?

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [October 21, 2026, 12:06pm UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/19 "2026-10-21T12:06:30Z")

</div>

@androiddev123 seems this should go out in the November release (ZOOM-1433531). Please check the [chanegelog](https://developers.zoom.us/changelog/) for Zoom Meetings next month for the fix.

---

<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:** [October 22, 2026, 12:07pm UTC](https://devforum.zoom.us/t/upcoming-meetings-api-returns-an-empty-response/145937/20 "2026-10-22T12:07:25Z")

</div>

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