Meeting SDK Type and Version
Zoom Apps SDK (@zoom/appssdk) version 0.16, used in an in-client panel (Home URL surface).
App type: user-managed General app (Meetings + Chat).
Development Client ID: wLuVDhBjSnOjl4G2lj2ndA.
Description
We are building a Zoom App with an in-client panel. A user opens the panel and needs to sign in to their Leap account through our external identity provider. We already read the signed x-zoom-app-context header successfully to establish the Zoom identity. The only remaining step is to open our hosted sign-in page, for which we need either openUrl (open the system browser) or the in-client authorize flow.
The problem is that both APIs come back as unsupported. zoomSdk.config() reports them in unsupportedApis, so we have no working way to launch our sign-in page (window.open is also blocked inside the webview). We would like to understand what provisioning or configuration is required to enable them.
Error?
zoomSdk.config({ version: '0.16', capabilities: [...] }) returns:
inMeetingcontext:unsupportedApis: ["authorize", "onAuthorized", "openUrl"]inMainClientcontext:unsupportedApis: ["authorize", "getMeetingContext", "onAuthorized", "openUrl"]
Calling authorize then throws:
app_not_support [80004]
Calling openUrl resolves successfully but the client never opens the URL.
Troubleshooting Routes
- Enabled the In-Client OAuth toggle on the Surface page.
- Removed and re-added the app (Local Test install).
- Tested in the main client, not only in a meeting.
- Fully updated the Zoom desktop client.
- Reviewed available scopes: the only Zoom App scopes offered are
zoomapp:inmeetingandzoomapp:inwebinar; we found nothing related toopenUrlorauthorize. - Added our sign-in domain to the Domain Allow List and configured the OAuth Redirect URL.
- Compared against Zoom’s official sample apps (the advanced-sample React Zoom App), which use
openUrlfor exactly this external-auth flow.
How To Reproduce
- Authentication method / app type: user-managed General app (Meetings + Chat), In-Client OAuth enabled, installed via Local Test. Panel loads at the Home URL and calls
zoomSdk.config()with capabilities includingopenUrl,authorize, andonAuthorized. - Errors:
config()returns those three APIs inunsupportedApis(both contexts);authorize()throwsapp_not_support [80004];openUrl()resolves but does nothing. - Browser / client type and version: Zoom desktop client [fill in your exact version], Zoom Apps SDK 0.16.
Questions
- What provisioning, feature flag, or configuration enables
openUrlandauthorizefor our app, beyond the In-Client OAuth toggle? - Is there a reason these would be ungranted for a user-managed General app on the Development config / Local Test install specifically?
- For opening an external hosted sign-in page from the in-client panel, which API is the recommended path, and what is the exact config to enable it?