Clarification on deleting users with recording transfer, inactive users, and recording inventory via Zoom APIs

API and Webhooks
,
1

API-Based User Deletion with Recording Transfer

We have tested the following API endpoint:

DELETE /v2/users/{userId}
?action=delete
&transfer_email=<archive-user>
&transfer_recording=true
&transfer_meeting=true

In practice, this appears to delete the user and transfer cloud recordings and meetings in a single operation.

Questions:

  1. Does this API officially guarantee transfer of all cloud recordings owned by the user?

  2. Does this API work for:

    • Active users only, or

    • Both active and deactivated users?

  3. If all recordings are transferred, is there any supported way to validate this programmatically after deletion?

Admin Account Handling

During our POC, we observed challenges related to Admin users.

Questions:

  1. Is Admin-to-Member role downgrade via API officially supported?

  2. If role downgrade is not supported or restricted, what is the recommended approach for offboarding Admin users while preserving recordings?

Recording Inventory and Discovery

Tenant-level

  • Is there a supported API or report that returns a list of users who currently own cloud recordings in a Zoom tenant?

  • If not, is enumerating recordings per user the expected approach?

User-level

For a specific user:

  • Is there a supported API method to retrieve:

    • The total number of meetings that have cloud recordings?

    • The number of recording files per meeting ?

  • If aggregation is not provided, can you confirm that counting:

    • meetings[] and

    • recording_files[]
      from the recordings API response is the correct and supported approach?

OAuth Scopes (End-to-End Automation)

To ensure our OAuth app is configured correctly, we would appreciate confirmation on:

  • What are the minimum required OAuth scopes to:

    • Search users

    • Identify user roles

    • Downgrade Admin users (if applicable)

    • Transfer recordings and meetings

    • Delete users

  • Are there any scopes that are commonly overlooked for this use case?

Primary Concern

Our primary concern is ensuring no cloud recordings are missed or lost during offboarding, especially when users are already deactivated prior to cleanup. We want to avoid relying on undocumented or unsupported behavior.

What We’re Looking For

  • Confirmation of supported behavior

  • Clarification of limitations

  • Best-practice recommendations for enterprise offboarding

  • Links to official documentation or KB articles