Server-to-Server OAuth App: `meeting:read:summary:admin` scope still not available in scope picker (2 years after #99179)

API and Webhooks
,
1

Hi Zoom Developer Team,

We are experiencing the same issue described in the now 2-year-old Forum thread:

The scope meeting:read:summary:admin does not appear in our Server-to-Server
OAuth App’s scope picker, so we cannot enable the
GET /v2/meetings/{meetingId}/meeting_summary endpoint.

The 2023 thread’s last reply (2023-12-12) said the rollout was “planned for
this week”, but the scope is still unavailable for us in May 2026 — over two
years later.

We have already been routed through Zoom support multiple times:

  • Customer Success (2026-05-19): advised us to file a Technical Support ticket
  • Technical Support TS2339087 (2026-05-24): closed as configuration-related,
    outside their scope; advised to use Developer Forum
  • Customer Success again (2026-05-25): confirmed this is Developer Team’s
    responsibility, asked us to ask via this Forum

Could the Zoom Developer team please:

  1. Confirm the current status of the meeting:read:summary:admin scope rollout
  2. Enable this scope for our Server-to-Server OAuth App

We’re happy to share our Account Number, App credentials, and any other
private details via direct message upon request from a Zoom representative.

Thank you for your support.

Takao Tatematsu
GMO Pepabo, Inc.

2

@takao sorry about your experience.

For meeting:read:summary:admin you can find this scope in newly create S2S OAuth apps

image
image804×684 76.9 KB

3

Hi @chunsiong.zoom,

Thanks for the reply.

Unfortunately, with help from our internal Zoom administrator, I’ve now
confirmed that meeting:read:summary:admin is still not available for
our account — even on a newly-created Server-to-Server OAuth App.

What we tested today

Test 1 — Existing S2S OAuth App (created on 2026-05-15)

The scope picker does not show meeting:read:summary:admin under the
Meeting category.

Test 2 — Brand-new S2S OAuth App created today (2026-05-28)

We created a fresh S2S OAuth App in the same Zoom account and opened
its scope picker. meeting:read:summary:admin is still not listed.

Test 3 — Keyword search inside the picker

Our administrator also tried searching the scope picker with just the
keyword “summary” — no matching scopes were returned. So the scope
doesn’t appear to exist in the catalog presented to our account at all,
not just be hidden somewhere.

(Note: I tried to attach screenshots of both scope pickers, but
Discourse blocked the upload with “Sorry, you can’t embed media items
in a post” — presumably because my account is new on this forum. I’m
happy to share the screenshots via DM.)

Request

Could you please check on Zoom’s side whether
meeting:read:summary:admin has actually been rolled out to our
account, and if not, enable / unlock it for us?

I’d prefer not to post our Account ID / Account Number / App credentials
on a public forum. If you can DM me, I’m happy to share whatever
account-level details and screenshots you need to look this up on your
side.

For context on the use case: we want to call
GET /v2/meetings/{meetingId}/meeting_summary to retrieve AI Companion
meeting summaries that only exist in users’ personal Zoom Hub area —
i.e. ones that don’t surface via recording_files. We already use the
cloud_recording:read:list_recording_files:admin +
file_type=SUMMARY route for the Smart Recording case, but it doesn’t
cover the personal-Zoom-Hub-only ones.

Thanks again — we’ve already been routed through Zoom Customer Success
and Technical Support multiple times before being told to post here, so
any direct enablement you can do would be hugely appreciated.

Best regards,
Takao Tatematsu

4

@takao sorry about that, i have misread this. This scope is available in General App, Account Managed

image
image728×595 28.6 KB