**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
Acquire an access token by going through any appropriate authentication flow. We used the device code flow.
Schedule a few meetings on your Zoom account.
Use the access code form the previous step to make a request to the API linked above.
How distant are the upcoming meetings? List upcoming meetings is documented with a time range of 24 hours, while List meetings with a directional type is documented with a time range of 6 months.
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:
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 for additional insights?
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
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.
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.
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 .
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.
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.
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.
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.
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
Thank you for testing both endpoints and clarifying that you get the scheduled meetings within the next 24 hours for List meetings, but not for List 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?
I will also ask the dev team why there is both type:upcoming and type:upcoming_meetings as they seem like unnecessary redundancies.
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.
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?
