# Access & aggregate Zoom survey responses via API

**URL:** <https://devforum.zoom.us/t/access-aggregate-zoom-survey-responses-via-api/56655>\
**Category:** Feature Requests\
**Created:** [August 30, 2021, 1:37pm UTC](https://devforum.zoom.us/t/access-aggregate-zoom-survey-responses-via-api/56655 "2021-08-30T13:37:02Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![cwhiteman](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cwhiteman/32/30611_2.png) [@cwhiteman](https://devforum.zoom.us/u/cwhiteman)\
**Post date:** [August 30, 2021, 1:37pm UTC](https://devforum.zoom.us/t/access-aggregate-zoom-survey-responses-via-api/56655/1 "2021-08-30T13:37:02Z")

</div>

**Describe the solution you’d like**  
We would like to serve a standard survey at the end of each meeting. This leads to two questions:

1. Is there a way to SAVE and re-use a survey (so meeting organizers don’t have to recreate it every time)?
2. Is there a way to retrieve and aggregate these survey responses across meetings (into a report) via API?

---

<div class="post-metadata">

**Author:** ![AlphaIIWebinars](https://avatars.discourse-cdn.com/v4/letter/a/ea666f/32.png) [@AlphaIIWebinars](https://devforum.zoom.us/u/AlphaIIWebinars)\
**Post date:** [October 26, 2021, 6:25pm UTC](https://devforum.zoom.us/t/access-aggregate-zoom-survey-responses-via-api/56655/2 "2021-10-26T18:25:29Z")

</div>

I’m looking for this too. We are retrieving our zoom data via api and having our webinar participants complete a post-webinar survey built in zoom. Unfortunately we can only get the survey responses via csv report by manually exporting after every webinar. Are there any plans for a Get Post Webinar Survey data api call?

---

<div class="post-metadata">

**Author:** ![pentalfa](https://avatars.discourse-cdn.com/v4/letter/p/47e85d/32.png) [@pentalfa](https://devforum.zoom.us/u/pentalfa)\
**Post date:** [October 28, 2021, 2:16pm UTC](https://devforum.zoom.us/t/access-aggregate-zoom-survey-responses-via-api/56655/3 "2021-10-28T14:16:22Z")

</div>

Also interested in both of these!

---

<div class="post-metadata">

**Author:** ![maxm87](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm87/32/45332_2.png) [@maxm87](https://devforum.zoom.us/u/maxm87)\
**Post date:** [February 13, 2023, 12:19am UTC](https://devforum.zoom.us/t/access-aggregate-zoom-survey-responses-via-api/56655/4 "2023-02-13T00:19:43Z")

</div>

Also interested in this!

---

<div class="post-metadata">

**Author:** ![turvak](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/turvak/32/45250_2.png) [@turvak](https://devforum.zoom.us/u/turvak)\
**Post date:** [August 31, 2023, 9:22am UTC](https://devforum.zoom.us/t/access-aggregate-zoom-survey-responses-via-api/56655/5 "2023-08-31T09:22:36Z")

</div>

+1 PLEASE this is a data report and should be exposed like the others

---

<div class="post-metadata">

**Author:** ![raj.rao](https://avatars.discourse-cdn.com/v4/letter/r/90db22/32.png) [@raj.rao](https://devforum.zoom.us/u/raj.rao)\
**Post date:** [October 3, 2023, 9:27pm UTC](https://devforum.zoom.us/t/access-aggregate-zoom-survey-responses-via-api/56655/6 "2023-10-03T21:27:28Z")

</div>

+1. This is definitely a required feature. We need to load the responses via the API so that we can build custom reports that brings together data from other systems.

---

<div class="post-metadata">

**Author:** ![zoom77](https://avatars.discourse-cdn.com/v4/letter/z/eada6e/32.png) [@zoom77](https://devforum.zoom.us/u/zoom77)\
**Post date:** [October 8, 2023, 8:36pm UTC](https://devforum.zoom.us/t/access-aggregate-zoom-survey-responses-via-api/56655/7 "2023-10-08T20:36:07Z")

</div>

+1  
Also interested in this!

---

<div class="post-metadata">

**Author:** ![akgorrell](https://avatars.discourse-cdn.com/v4/letter/a/cab0a1/32.png) [@akgorrell](https://devforum.zoom.us/u/akgorrell)\
**Post date:** [November 19, 2024, 9:43pm UTC](https://devforum.zoom.us/t/access-aggregate-zoom-survey-responses-via-api/56655/8 "2024-11-19T21:43:07Z")

</div>

+1 also interested in this.
