# Webinar participant data is inaccurate **URL:** \ **Category:** API and Webhooks\ **Created:** [May 11, 2020, 10:32am UTC](https://devforum.zoom.us/t/webinar-participant-data-is-inaccurate/17062 "2020-05-11T10:32:11Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![priya.jetley](https://avatars.discourse-cdn.com/v4/letter/p/b3f665/32.png) [@priya.jetley](https://devforum.zoom.us/u/priya.jetley)\ **Post date:** [May 11, 2020, 10:32am UTC](https://devforum.zoom.us/t/webinar-participant-data-is-inaccurate/17062/1 "2020-05-11T10:32:11Z")
Hello, We have been retrieving participant data for webinars since January using the below URLs - [https://api.zoom.us/v2/metrics/webinars/occurence\_id/participants?type=past&page\_size=300](https://api.zoom.us/v2/metrics/webinars/occurence_id/participants?type=past&page_size=300) [https://api.zoom.us/v2/report/webinars/occurence\_id/participants?type=past&page\_size=300](https://api.zoom.us/v2/report/webinars/occurence_id/participants?type=past&page_size=300) The process to retrieve the data iterates through the list of occurrence ids of a webinar and retrieves participant data for each occurrence.However, recently we observed that when a webinar has more occurrence ids than the number of days it spans (maybe because the hosts laptop crashed so he had to restart the webinar or for some other reason) the data we fetch becomes inaccurate. We get lesser number of participants for that particular day. However, when we check the report on the Zoom website (Reports \> Usage Reports \> Webinar \> Attendee Report), it shows more participants. Would appreciate any help in resolving this issue. Thank you. Regards, Priya Jetley ---
**Author:** ![priya.jetley](https://avatars.discourse-cdn.com/v4/letter/p/b3f665/32.png) [@priya.jetley](https://devforum.zoom.us/u/priya.jetley)\ **Post date:** [May 12, 2020, 10:21am UTC](https://devforum.zoom.us/t/webinar-participant-data-is-inaccurate/17062/2 "2020-05-12T10:21:58Z")
Hello, Any updates/ suggestions regarding this issue? I would like to add that upon further examining the webinars with data issues I observed that only the webinars with occurrence ids with the ‘/’ character in them were the ones that failed to retrieve data. For example - Webinar Id : 316014643 Occurence Ids : /45rrzUAQBukO/9FsKN7Fw== (issue) Vk8kUQ2KSMCCcBWX4E8bbA== DKSyQyVHT/+o8Jo/uReKvQ== UBt3bxVlREiW85DPM3vIHA== Webinar Id - 531155155 Occurence Ids : fngmMZG4SmuCxGUFtWGyaQ== LZAFIaCmQeiGxZVQS9C5/w== Zy6zkU//TMazCboearSNAA== (issue) ar1ze0ulSEGDg2701pSC1A== Webinar Id - 524967002 Occurence Ids : HmTq57wTQqa0iuFhtauPjg== waeFVe1CTFmxzC+cFiAhcA== nF2gU5WKSnmEuVdsXdWWNw== /EusDjUtSCKkqOHHPG7RjQ== (issue) This is however surprising because in my PL/SQL procedure I use the **APEX\_UTIL.URL\_ENCODE(trim(occurence\_id))** function when constructing the API URL. I can also attach the PL/SQL procedure if someone would like to review it for issues. Would appreciate a prompt response on this as we are in the process of collating data and this is becoming a big issue. Thanks very much. Best Regards, Priya ---
**Author:** ![priya.jetley](https://avatars.discourse-cdn.com/v4/letter/p/b3f665/32.png) [@priya.jetley](https://devforum.zoom.us/u/priya.jetley)\ **Post date:** [May 13, 2020, 5:06pm UTC](https://devforum.zoom.us/t/webinar-participant-data-is-inaccurate/17062/3 "2020-05-13T17:06:39Z")
Attaching screenshots of my procedures for your reference. Thanks! Priya ![procedure_get_webinar_part_report](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/2X/5/5400ced5a0c60190900b2c390f46a8f8b2751d2b.png) ![procedure_get_participant_details](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/2X/b/b053347f761d2d5aee6ebc36ccd8dafb408f38a8.png) ![procedure_get_participants](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/2X/5/579c2ed6933fe58062cc0704d65579cead82fb2f.png) ---
**Author:** ![priya.jetley](https://avatars.discourse-cdn.com/v4/letter/p/b3f665/32.png) [@priya.jetley](https://devforum.zoom.us/u/priya.jetley)\ **Post date:** [May 14, 2020, 2:05pm UTC](https://devforum.zoom.us/t/webinar-participant-data-is-inaccurate/17062/4 "2020-05-14T14:05:39Z")
Hello, Any updates on this thread. I tested the above URLs in Postman and I get and an error - { “code”: 3001, “message”: “Meeting does not exist: 45rrzUAQBukO/9FsKN7Fw==.” } It seems as though the “/” at the beginning is ignored and therefore the occurrence id cannot be located in this case. For occurrence id : Zy6zkU//TMazCboearSNAA== { “code”: 3001, “message”: “Meeting does not exist: Zy6zkU/TMazCboearSNAA==.” } For occurrence id : /EusDjUtSCKkqOHHPG7RjQ== { “code”: 3001, “message”: “Meeting does not exist: EusDjUtSCKkqOHHPG7RjQ==.” } ---
**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\ **Post date:** [May 19, 2020, 4:19pm UTC](https://devforum.zoom.us/t/webinar-participant-data-is-inaccurate/17062/5 "2020-05-19T16:19:53Z")
Hey @priya.jetley, Please [double url encode](https://www.urlencoder.org/) any webinarUUID’s with a slash in it. For example, `/EusDjUtSCKkqOHHPG7RjQ==` becomes `%252FEusDjUtSCKkqOHHPG7RjQ%253D%253D` Try that and it should work. 🙂 Thanks, Tommy ---
**Author:** ![priya.jetley](https://avatars.discourse-cdn.com/v4/letter/p/b3f665/32.png) [@priya.jetley](https://devforum.zoom.us/u/priya.jetley)\ **Post date:** [May 20, 2020, 12:11pm UTC](https://devforum.zoom.us/t/webinar-participant-data-is-inaccurate/17062/6 "2020-05-20T12:11:01Z")
Hi Tommy, Thanks for your answer, I tried the following in my procedure and was able to fetch the report data for the occurrence Ids I mentioned above - l\_url :=‘[https://api.zoom.us/v2/metrics/webinars/](https://api.zoom.us/v2/metrics/webinars/)’ || APEX\_UTIL.URL\_ENCODE(APEX\_UTIL.URL\_ENCODE(trim(p\_occurence\_id))) || ‘/participants?type=past&page\_size=300’; I might be overthinking this, but can this double encoding impact our future data pulls adversely in anyway?I mean with regards to other reserved characters/ non reserved characters. Thanks very much! I have marked this solved. Best Regards, Priya ---
**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\ **Post date:** [May 26, 2020, 7:49pm UTC](https://devforum.zoom.us/t/webinar-participant-data-is-inaccurate/17062/7 "2020-05-26T19:49:05Z")
Happy to hear your issue is resolved! 🙂 > [@priya.jetley](#): > > I might be overthinking this, but can this double encoding impact our future data pulls adversely in anyway?I mean with regards to other reserved characters/ non reserved characters. It should not impact future data pulls. We do plan on fixing the slash issue at some point. On the off chance it is a breaking change, we will communicate this well in advance. Thanks, Tommy ---
**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\ **Post date:** [August 21, 2020, 9:31pm UTC](https://devforum.zoom.us/t/webinar-participant-data-is-inaccurate/17062/8 "2020-08-21T21:31:45Z")
Closed on August 21, 2020, 9:31pm UTC