We are encountering an issue with the Zoom API for fetching participants.
Most of the time, the API only returns a subset of the list. However, when we log in and download the list from a host’s account, we are able to retrieve the entire list.
I wanted to share this to see if this is a common issue that others have faced. Any help in resolving this would be greatly appreciated.
For reference, we have used both of the following APIs to fetch the participant list w/o much success:
Hi @subrat
Thanks for reaching out to the Zoom Developer Forum and welcome to our community!
Have you been able to troubleshoot this issue? If not, could you share with me some examples of what you are getting to take a look at it?
Cheers,
Elisa
However step 4 is where we are still seeing a subset of webinars/meetings return participant data that is incomplete (only partial attendance data included). Later in the day if the client runs the report directly in zoom, the data is there, but it is not available within 1-3 minutes after the event. This causes major issues for clients who rely on the automated system to process attendance data and grant users credits automatically. When there is a delay, significant end-user support issues are encountered.
Hi @jkendall
Thanks for reaching out.
I will go ahead and close the other thread so we can keep the communication just in one post.
I believe this issue could be due to the way you are calling the report endpoint. The data takes somewhere between 1 to 2 minutes to process, so instead of calling the Report endpoint immediately after the meeting or webinar ended, I would encourage you to delay this call to get all the data.
But allow me some time to do some testing on my end to troubleshoot this.
Cheers,
Elisa
We have tried to add in delays. The issue is the results are very inconsistent (sometimes available in 1 min, and every so often much longer (10min?). And the OP’s issue happens to us as well. The endpoint will return data right way, it is just partially incomplete and there is no indication that it’s still processing, just random missing data which makes it hard to rely on the output of the endpoint.