Hi all,

I'm having trouble with the Zoom API and could use some help. I've created a Zoom Marketplace app with a wide range of permissions and can successfully complete the server-to-server oauth login and make some basic API requests.

However, I'm running into an issue with account-level API calls (e.g., GET /accounts/*). Zoom responds with a scope-related error:

{
  "code": 4711,
  "message": "Invalid access token, does not contain scopes:[meeting:read:meeting:master]"
}

I have double-checked that this scope (meeting:read:meeting:master) is enabled in the app configuration, and I can also see it included in the /oauth/token response.

What could be causing this? Are there specific requirements for either:

• The app itself (e.g., app type or configuration)?

• The user creating the app and collecting the client ID/secret?

For context, I’m an admin on the Zoom account, but not the owner. I assumed being an admin would be sufficient to authorize account-level API requests — is that incorrect?

Appreciate any insights, thanks!

I'm playing around with the Zoom SDK for my app, and I've hit a bit of a snag when trying to join meetings hosted by other Zoom accounts. I keep getting this "Error Code: 4011" that basically says my SDK app needs to be published on the Zoom Marketplace.

Now, I get why that might be a thing for big, public apps. But honestly, my use case is pretty specific and more on the internal/controlled side. Creating and maintaining a full-blown public app on the Marketplace just for this seems like overkill.

So, my question to you all is: Is there ANY way around this? Has anyone figured out a clever trick or a different kind of integration that lets you use the Zoom SDK to join external meetings without having to go through the whole "publish to Marketplace" song and dance?

I'm talking about things like private apps, internal integrations, or maybe some hidden config I'm missing. Anything that avoids the public marketplace hassle would be amazing!

Seriously, any tips, workarounds, or even just a "nope, you're stuck!" would be super helpful.

What I’m trying to do
I’m building a Meeting-Component app that uses the Zoom Apps SDK’s video_layer APIs to overlay a “✓” on the camera feed.  my manifest.json needs an "app_id" set to my SDK Key (App ID).

What I’ve done so far

1. In the Zoom Marketplace → Develop → Build App, I selected User-managed app → Meeting SDK (sometimes labeled “Zoom App SDK” or “Meeting Component”).

2. Filled out Basic Information, Surface, Embed, Connect, Scopes (only zoomapp:inmeeting), and Local Test → Add App.

3. In the App Credentials panel I see Client ID / Client Secret (for OAuth), but no SDK Key or SDK Secret fields.

4. I opened the Basic Info, Access, Surface, Embed, Connect, Scopes sections again—still only OAuth credentials.

5. Developer Mode is enabled in the Zoom client and I can load my manifest in-meeting, but all zoomSdk calls silently fail because app_id isn’t set.
   
   

   What I expected

   • A section at the top of App Credentials showing SDK Key (App ID) and SDK Secret, which I can copy into my manifest.json.

   • Documentation indicates Meeting SDK apps use JWT via the SDK Key/Secret, so those values must exist somewhere.

   What actually happens

   • Only OAuth Client ID/Secret are shown under App Credentials.

   • No “SDK Key” or “App ID” label is visible anywhere in the UI.
     
     

     Question

     1. Where can I find or enable the SDK Key (App ID) and SDK Secret for a Meeting SDK app in the Zoom App Marketplace?

     2. Has the Marketplace UI for Meeting-Component apps changed recently?

     3. Any additional steps I’m missing to surface those fields?

Hello. I am an engineer currently trying to create a system that uses webhooks to send notifications to Slack when a call on Zoom Phone is missed, based on a request from our sales team. Specifically, the plan is to trigger a GCP Cloud Function endpoint with the webhook, which in turn sends a notification to Slack.

Although I've managed to send notifications to Slack by using the verification button on Zoom Phone, I'm not sure how to actually integrate Zoom Phone with the webhook I've created. In my research, even for internal use, it seems that we need to apply for and obtain approval from Zoom for the webhook. I'm also struggling with how to deploy and install it for use by other employees, as I haven't been able to validate it in a production environment.

If anyone knows anything about this, I would appreciate your guidance.

Hey,

Just wondering, if we make any changes to our published apps, especially user-managed OAuth apps, do we need to unpublish them first? We updated the OAuth redirect URL in our app, and since then, we've been getting an "Invalid redirect - 4,700" error, even though we're using the correct URL.

Any help on this would be really appreciated.

Thanks.

My timer has looked like this for quite a while now — something seems to be broken in its interface. Reinstalling both Zoom and the timer app doesn’t help. Switching from dark to light theme doesn’t fix it either. Minimizing and popping the app out (Pop out) doesn’t help either. Could you help me fix this? 

I'm using Windows 11 64-bit.

Our app uses the Print dialog to print a document after our app flow finishes.

The Zoom Embedded browser doesn't respect "Landscape" css directive, and there isn't a way to manually print in Landscape mode.

There doesn't seem to be any place I can find to submit a bug report.

Here is what it looks like - the layout direction buttons are not clickable.