Hello Zoom Developer Community,
I am hoping for some urgent help from a Zoom staff member regarding a critical account issue that is completely blocking my Video SDK integration. I have confirmed my implementation is correct and that the issue lies with my account’s configuration on Zoom’s end.
The Goal: To use the Video SDK to create a custom video session in my web application.
The Problem: My application successfully generates a signature from my backend, but when the frontend client calls client.join(...), it immediately fails with the following error from the Zoom SDK:
{
type: 'JOIN_MEETING_FAILED',
reason: 'This account does not exist or does not belong to you',
errorCode: 200
}
My Account Status (Confirmed via Screenshots):
-
I have a paid Zoom Workplace Pro account.
-
My user is correctly assigned the “Licensed” status.
-
I have an active Video SDK Pay As You Go (CPaaS) plan.
The Root Cause (Strongly Suspected): After extensive debugging, I think I have discovered a critical anomaly in my account’s configuration. In my Zoom account portal, under “Basic Information” for my CPaaS plan, my account is listed with my own name as the “Reseller Partner.”
I am not a reseller. I am a developer using the CPaaS plan directly for my application. Based on what I have seen, this incorrect “Reseller Partner” status has likely provisioned my account as a “Master Account,” which is architecturally incompatible with the direct authentication flow required by the Video SDK.
Evidence & Due Diligence Performed:
-
Correct Credentials: I have repeatedly verified that the SDK Key and SDK Secret I am using are from the correct Video SDK app on the correct, paid Zoom account.
-
Working Backend: My Firebase Cloud Function is working perfectly. The server-side logs definitively show that it is loading the correct, full SDK Key and successfully generating a signature.
-
Working Frontend: My React application is working perfectly. It successfully receives the signature from the backend and passes it to the SDK.
-
The Error is from Zoom: The failure is happening at the final step, when the SDK communicates with Zoom’s servers.
This is not an implementation error in my code. It is a systemic authorisation failure caused by an incorrect account type on Zoom’s backend.
Could a Zoom staff member please investigate my account and correct the provisioning error by removing the “Reseller Partner” status? This is the only remaining blocker, and I have exhausted all other support channels.
Thank you for your time and assistance.