# Server-to-Server OAuth app can't access meeting\_summary:read:admin

**URL:** <https://devforum.zoom.us/t/server-to-server-oauth-app-cant-access-meeting-summaryadmin/99844>\
**Category:** API and Webhooks\
**Created:** [December 8, 2023, 10:56pm UTC](https://devforum.zoom.us/t/server-to-server-oauth-app-cant-access-meeting-summaryadmin/99844 "2023-12-08T22:56:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tawana.lederman](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tawana.lederman/32/54687_2.png) [@tawana.lederman](https://devforum.zoom.us/u/tawana.lederman)\
**Post date:** [December 8, 2023, 10:56pm UTC](https://devforum.zoom.us/t/server-to-server-oauth-app-cant-access-meeting-summaryadmin/99844/1 "2023-12-08T22:56:40Z")

</div>

We have created a Server-to-Server OAuth app, including the user:read:admin, meeting:read:admin and meeting\_summary:read:admin scopes. When generating an Access Token through the [zoom.us/oauth/token](http://zoom.us/oauth/token) endpoint with the app’s “client\_id” and “client\_secret”, and requesting the “account\_credentials” grant\_type, the scopes returned for the Access Token only include user:read:admin and meeting:read:admin. It fails to show that the meeting\_summary:read:admin scope was enabled for that server-to-server app.

How can we ensure the Svr-to-Svr OAuth app has access to the meeting\_summary resource, across Users?

---

<div class="post-metadata">

**Author:** ![abhishek-coda](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/abhishek-coda/32/37244_2.png) [@abhishek-coda](https://devforum.zoom.us/u/abhishek-coda)\
**Post date:** [December 9, 2023, 9:50pm UTC](https://devforum.zoom.us/t/server-to-server-oauth-app-cant-access-meeting-summaryadmin/99844/2 "2023-12-09T21:50:48Z")

</div>

This is probably the cause:

> [@Scope meeting\_summary:read:admin doesn't show up on the Developer App section](https://devforum.zoom.us/t/scope-meeting-summaryadmin-doesnt-show-up-on-the-developer-app-section/99179/6):
>
> @danielolarte Apologies for the inconvenience here. The scopes were not deployed. We are deploying the scopes this week. I will update here when the scopes are deployed. Appreciate your patience

---

<div class="post-metadata">

**Author:** ![ojus.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ojus.zoom/32/734_2.png) [@ojus.zoom](https://devforum.zoom.us/u/ojus.zoom)\
**Post date:** [December 12, 2023, 4:55am UTC](https://devforum.zoom.us/t/server-to-server-oauth-app-cant-access-meeting-summaryadmin/99844/3 "2023-12-12T04:55:58Z")

</div>

> [@Important Update for Zoom API Users: Ongoing Issue with Meeting Summary Scopes](https://devforum.zoom.us/t/important-update-for-zoom-api-users-ongoing-issue-with-meeting-summary-scopes/99961):
>
> Dear Zoom Developer Community, We hope this message finds you well. We are writing to address a recent issue many of you have encountered regarding the Zoom API, specifically concerning the meeting\_summary:read:admin and meeting\_summary:read scopes. Current Situation: Despite having enabled all necessary settings and correctly selecting the aforementioned scopes within your server-to-server OAuth apps, it has come to our attention that there is a persistent issue preventing successful API call…

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [December 13, 2023, 4:56am UTC](https://devforum.zoom.us/t/server-to-server-oauth-app-cant-access-meeting-summaryadmin/99844/4 "2023-12-13T04:56:21Z")

</div>

Closed on December 13, 2023, 4:56am UTC

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
