# OAuth Reports API scope issue

**URL:** <https://devforum.zoom.us/t/oauth-reports-api-scope-issue/20933>\
**Category:** API and Webhooks\
**Created:** [June 10, 2020, 2:06pm UTC](https://devforum.zoom.us/t/oauth-reports-api-scope-issue/20933 "2020-06-10T14:06:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![edu\_dev4](https://avatars.discourse-cdn.com/v4/letter/e/ad7895/32.png) [@edu\_dev4](https://devforum.zoom.us/u/edu_dev4)\
**Post date:** [June 10, 2020, 2:06pm UTC](https://devforum.zoom.us/t/oauth-reports-api-scope-issue/20933/1 "2020-06-10T14:06:04Z")

</div>

**Description**  
The /report/meetings/{meetingId}/participants API endpoint requires scope: report:read:admin. However, this scope is not selectable within OAuth API App Scopes.

How do we use the Reports API if we can’t select the scope?

---

<div class="post-metadata">

**Author:** ![michael.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael.zoom/32/37213_2.png) [@michael.zoom](https://devforum.zoom.us/u/michael.zoom)\
**Post date:** [June 13, 2020, 12:32am UTC](https://devforum.zoom.us/t/oauth-reports-api-scope-issue/20933/2 "2020-06-13T00:32:28Z")

</div>

Hi @edu_dev4 to select Admin level scopes, your OAuth will need to be Account-level. The app you have created is likely User-managed.

---

<div class="post-metadata">

**Author:** ![edu\_dev4](https://avatars.discourse-cdn.com/v4/letter/e/ad7895/32.png) [@edu\_dev4](https://devforum.zoom.us/u/edu_dev4)\
**Post date:** [June 15, 2020, 2:19pm UTC](https://devforum.zoom.us/t/oauth-reports-api-scope-issue/20933/3 "2020-06-15T14:19:08Z")

</div>

Thank you Michael. We did go with the User-Level app. I am hoping there will be some way around this in the future, as we want to use the reporting features, but do not want all users in our organization to be Admin-Level users. That introduces massive security vulnerabilities.

As an example, say we have 300 teachers in our district who run 7-10 meetings per day. We want these teachers to be able to look at advanced meeting report stats within our UI, but do not want them to be able to have admin access to our entire district Zoom organization. In particular, we don’t want them being able to invite, remove, or view any information about other users in the organization.

The simplest solution would be to allow the authenticated user to access their own reports, with a /me/ indicator. This has precedent in others areas of the API.

/report/meetings/me/{meetingId}/participants

We are adding this idea to the growing list of ideas for Zoom product improvement!

---

<div class="post-metadata">

**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:** [June 18, 2020, 8:10pm UTC](https://devforum.zoom.us/t/oauth-reports-api-scope-issue/20933/4 "2020-06-18T20:10:30Z")

</div>

Hey @edu_dev4,

Thanks for your suggestions, I agree we should offer users access to their own reports via the API. Feel free to submit this as a feature request here: #feature-requests

In the meantime, you can use the [Get Past Meeting Participants endpoint](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/pastmeetingparticipants) with a user level OAuth app to see who participated in the meeting.

-Tommy

---

<div class="post-metadata">

**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, 10:08pm UTC](https://devforum.zoom.us/t/oauth-reports-api-scope-issue/20933/5 "2020-08-21T22:08:12Z")

</div>