User-level OAuth: API access to AI Companion summaries and transcripts for meetings I ATTENDED but did not host

Zoom Apps
1

I’m building an internal Claude-based assistant that pulls Zoom AI Companion summaries and transcripts after each meeting and merges them with my notes. I want each user in my company to install this assistant and access only their own meeting data.

I’ve confirmed that a Server-to-Server OAuth app with meeting:read:summary:admin and cloud_recording:read:meeting_transcript:admin works perfectly, but it gives EVERY install full account-wide access, which is a non-starter for sharing the assistant with employees.

A User-level OAuth app (with the non-admin equivalents) is the natural fit, except I can’t confirm whether it returns data for meetings the authenticated user attended but did not host.

Specific endpoints in question (called with a user-level OAuth token, where the authenticated user was an attendee, not the host):

  • GET /v2/meetings/{meetingUUID}/meeting_summary

  • GET /v2/meetings/meeting_summaries

  • GET /v2/meetings/{meetingUUID}/transcript

Questions:

  1. Will any of those endpoints return data for a meeting the authenticated user attended but did not host?

  2. If not, is there a planned roadmap item for participant-scoped access to AI Companion artifacts? Michael flagged this on the roadmap in 2020 (this thread: https://devforum.zoom.us/t/is-it-possible-to-list-all-the-meetings-ive-attended-using-the-api/17046).

  3. Is there ANY official path that lets each employee in an organization read their own AI Companion summaries (host AND attended) via API, without giving them account-wide admin scopes?

2

I would not design this as participant-scoped access today. Zoom describes GET /v2/meetings/meeting_summaries as List an account’s meeting or webinar summaries and requires an admin summary scope, so that one is not a per-user attendee feed. GET /v2/meetings/{meetingId}/meeting_summary does support a user-level meeting summary scope, but Zoom documents host plan and host AI Companion settings as prerequisites, and does not state that an attendee’s OAuth token can read summaries for meetings they did not host.

For transcripts, GET /v2/meetings/{meetingId}/transcript is documented under Cloud Recording, returns a transcript download URL, and uses cloud recording transcript scopes. That points to recording-owner or admin-style access rather than a general “meetings I attended” transcript API. Zoom’s AI Companion API guidance also says AI Companion data is exposed through product-specific API endpoints, not a unified participant artifact API.

Instead, you could avoid host/admin-scoped Zoom artifacts altogether by using Recall’s Meeting Bot API to capture participant-authorized meeting data with one API request.