What the Meeting SDK does for your room
Your room runs your real meeting inside your own page, and the piece that makes that possible is the Zoom Meeting SDK. It is the official toolkit for running a meeting inside a website rather than in the desktop app. Your developer app is the key that lets your room use it for your account. Zoom is a trademark of Zoom Communications, Inc. BrandedRooms is an independent product and is not affiliated with or endorsed by Zoom.
Until the SDK is switched on and the app is activated, the app exists but has no permission to sign anyone into a meeting from a web page. Your room is set up correctly and waiting; it simply has nothing to sign with yet.
Once it is on, guests join inside your page in the browser, with nothing to download. Anyone who prefers the desktop app can still use the regular meeting link, exactly as before. Those people join the same meeting, but they will not see your page, your offers or your effects, which is one more reason to make the in-page room the link you share.
Step by step
Sign in first with the account that hosts your meetings. Then work through these in order.
- Go to marketplace.zoom.us, choose Develop, then Build App, and open the General App you created when connecting your account.
- Open the Features section of the app and choose Embed.
- Find Meeting SDK and switch it on. Save if the page asks you to.
- Open Local Test and press Add App Now. Approve the prompt. This activates the app on your account.
- Go back to your room settings and confirm the Client ID and Client Secret there are the ones from this same app.
- Run a guest test on a second device to confirm the meeting now opens inside your page.
The look-alike setting to leave alone
The Embed area has more than one switch, and one of them sounds right but is not. The option labelled Use public client OAuth is a different feature for a different kind of app. Turning it on does not enable embedding and can be left off. The switch you want is the one named Meeting SDK.
If you have already flipped the wrong one, switch it back off, switch Meeting SDK on, and repeat the Local Test step. Nothing else needs undoing.
One account, start to finish
The developer app must live in the same account that owns the meeting your guests will join. An app built in a colleague's account, a test account or a second company account cannot sign guests into your meeting, even if every switch is on. If your team hosts from a shared company account, build the app once in that account and use its keys in each room.
This is worth checking even when you are sure. Signing in to the marketplace with a personal login out of habit is the easiest way to end up with a perfectly configured app in the wrong place.
How to know it worked
Open your room in a private browser window, join as a guest with a test name and email, and wait in the lobby. Start the meeting in the app as host, then press Start the room in your control panel. If the guest's page switches to the live meeting by itself, the SDK is on and the app is active. If the guest still sees Signature is invalid, work through the fix page for that message, which covers the less common causes too.