Title: Video Management API: Channel permissions return internal hashed user_id that throws 404 on /users endpoint

API and Webhooks
1

Hello,

I am building an integration using Server-to-Server OAuth to sync users to Video Management channels. I’ve run into an “Identity Gap” issue when trying to verify existing channel owners and members.

It is worth noting that this integration was working perfectly up until recently. It seems the API behavior may have suddenly changed, causing this new error

The Issue: When I call GET /v2/video_management/channels/{channelId}/permissions, the API returns an internal, hashed string for the user_id instead of a standard Zoom User ID . Furthermore, the email field is frequently missing for the channel owner.

Example Response:

JSON

{
    "permissions": [
        {
            "user_id": "47377d0ae07741aabcda498b1059c561",
            "display_name": "John Doe",
            "role": "OWNER"
        }
    ]
}

Because the email is missing, I need to look up this user to map them to my local database. However, if I pass this hash into the standard users endpoint (GET /v2/users/47377d0ae07741aabcda498b1059c561), Zoom returns a 404:

JSON

{"code":1001,"message":"User does not exist: 47377d0ae07741aabcda498b1059c561."}

Current Workaround: Right now, I am forced to fall back to matching users by display_name, which is fragile and prone to breaking if users change their names or duplicate usernames.

My Questions:

  1. Is there an API endpoint or method to translate this Video Management hashed user_id back into a standard Zoom User ID or retrieve the associated email address or something similar?

  2. If not, is there a roadmap to include the email field consistently for all roles (including OWNER) in the permissions response?

Thank you for your time!