/v2/past_meetings/{meetingUUID}/archive_files endpoint

Hello Zoom Support Team,

We are still investigating the GET /v2/past_meetings/{meetingUUID}/archive_files endpoint.

Our account already has:

Meeting and Webinar Archiving enabled

Required archive scopes configured

Archive status completed

However, the response still only returns:

audio

video

chat

transcript files

The response does not include the physical_files field mentioned previously.

We would like to understand specifically:

Is there an additional account-level feature, admin setting, or support-enabled flag required for physical_files to appear in the response?

Is there a separate configuration for meeting attachments/assets shared during the session?

Does physical_files require a specific Zoom plan or add-on license?

Can you provide the exact admin path in the Zoom portal where this feature is enabled?

At the moment, attachments are visible in the Zoom UI under meeting assets, but they are not exposed through the API response.

Thank you.

Zoom’s API reference shows physical_files as a top-level field in the response for GET /past_meetings/{meetingUUID}/archive_files, with file_id, file_name, file_size, and download_url. That means attachments/assets are modeled separately from the normal archive_files array, which is typed for MP4, M4A, chat, captions, transcript, and JSON activity files.

The part that is not clearly documented is the enablement path for physical_files. Zoom’s portal docs only list archiving controls for video/shared screen, audio, in-meeting chat, and captions under Archive meetings and webinars. They do not document a separate attachment toggle, plan requirement, or support flag that proves when physical_files should appear.

Given your account already has archiving enabled and the assets are visible in the UI, I’d escalate this to Zoom Support and ask them to confirm whether physical_files requires a backend entitlement or whether this is an API response gap for your account.