Regression: /users/{userId}/recordings no longer returns My Notes recordings

Hi

We have an account-level integration that needs to retrieve the actual audio recordings created by My Notes for all users—not only My Notes documents, summaries, or transcripts.

These recordings appear in the Zoom web portal under:

Recording & Transcript Management → My Notes recordings

Previously, the following endpoint appeared to return these My Notes recordings alongside regular cloud recordings:

GET /v2/users/{userId}/recordings

It now appears to return only regular Zoom meeting cloud recordings.

For example, the web portal shows a completed My Notes recording for a user on July 20, 2026. We queried:

GET /v2/users/{userId}/recordings
    ?from=2026-07-20
    &to=2026-07-21

Using:

cloud_recording:read:list_user_recordings:admin

The request succeeds with HTTP 200, but returns:

{
  "total_records": 0,
  "meetings": []
}

We also tested a wider 30-day range with the same result. Standard meeting cloud recordings are still returned correctly, so this does not appear to be an authentication or recording-scope problem.

To be explicit, we need access to the My Notes recording objects, including:

  • Recording ID and owner
  • Recording date and duration
  • Processing status
  • Playback URL
  • Audio download URL
  • Any associated transcript, when available

We investigated the available alternatives:

  • Zoom Docs/Canvas APIs expose My Notes documents and transcripts, but these are not the audio recordings shown in the My Notes recordings tab.
  • The Docs My notes folder is unrelated to the recording catalog we need.
  • Zoom MCP’s search_meetings and get_meeting_assets appear to retrieve My Notes content and transcripts, not the standalone My Notes audio recording.
  • MCP’s get_recording_resource requires an ordinary cloud recording, as confirmed in this forum thread.
  • A user-managed OAuth app would require every account user to authorize separately, which does not meet our account-level ingestion requirement.

Could someone from Zoom clarify:

  1. Was removing My Notes recordings from /users/{userId}/recordings intentional?
  2. If so, when was this behavior changed or deprecated?
  3. Is there a replacement REST API, webhook, or MCP tool for listing and downloading My Notes audio recordings?
  4. Is there an account-wide/admin solution for retrieving these recordings for every user?
  5. Is my_notes:read:content:admin associated with an unpublished or early-access recording endpoint?
  6. If this was not intentional, can it be treated as a regression and escalated to engineering?

We can provide account IDs, user IDs, request timestamps, screenshots, and example recording details privately to Zoom staff. No access tokens will be posted.

Thank you.

Zoom currently documents GET /v2/users/{userId}/recordings as listing a user’s cloud recordings, with cloud-recording scopes and prerequisites. It does not document My Notes audio as part of that response. The earlier inclusion therefore was not a published API contract, there doesn’t seem to be a public changelog or deprecation notice confirming whether its removal was intentional or when it occurred.

The published Canvas APIs can expose My Notes document archives and transcript snapshots, but they do not expose playback or audio download URLs for standalone My Notes recordings. Zoom also confirmed that MCP get_recording_resource depends on an ordinary cloud recording, so it does not solve this issue. The granular scope reference does not map my_notes:read:content:admin to a public recording endpoint. There doesn’t seem to be documented REST API, webhook, MCP tool, or account-wide admin route for these audio objects.