Issue with Meeting Registrants Listing API - Empty response with or without Authorization

Description
We’re trying to access the Meeting registrants using the API
https://api.zoom.us/v2/meetings/{meetingUUID}/registrants [GET]

Error
By default the response of the API is empty with status code as 200. With or without authorization it is still the same.

Which App Type (OAuth / Chatbot / JWT / Webhook)?
OAuth based API authentication for https://api.zoom.us/v2/meetings/{meetingUUID}/registrants [GET]

Which Endpoint/s?
Any APIs which falls under the /meetings is affected by this issue.
Link to the API endpoint documentation https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/

How To Reproduce (If applicable)
Steps to reproduce the behavior:

  1. Above mentioned API
  2. Response code is 200 and is empty always

Screenshots (If applicable)

Additional context
This seems to be some sort of major issue with APIs. Please help

You can even try opening the below url from the browser directly, it will still load fine. Weird.

https://api.zoom.us/v2/meetings/nXaTgz6ORMiK/or5jU8x7g==/registrants?occurrence_id=deserunt%20officia&page_size=30&page_number=1&next_page_token=deserunt%20officia

(or)

https://api.zoom.us/v2/meetings/nXaTgz6ORMiK%2For5jU8x7g%3D%3D/registrants?occurrence_id=deserunt%20officia&page_size=30&page_number=1&next_page_token=deserunt%20officia

Hey @Nikhilesh,

Thank you for reaching out to the Zoom Developer Forum. Interestingly, I’m able to reproduce the issue with the URLs that you provided by when substituting my own Registration Required Meeting UUID I don’t see the same issue. I’ve reached out to our engineering team for clarification.

(ZOOM-311571)

Thanks,
Max

Hey @Nikhilesh,

Thank you for your patience. It looks like there are a couple of factors playing into this. First, the List Meeting Registrants API will only accept a Meeting ID as it expects to operate on a meeting occurrence in the future rather than a meeting instance in the past.

Further, because this UUID contains a slash, it caused the API to return a 200 OK status instead of an “Invalid Meeting ID” error.

From here, you should be able to use the Meeting ID along with the occurrence ID to refer to the meeting instances scheduled in the future that have been registered for.

I hope that helps! Let me know if you have any questions.

Thanks,
Max