[Resolved with 1.7.4+] Web SDK / Web Client from browser: 403 Forbidden

The main reason we decided to use ZOOM was based on the possibility to join Meetings without the need to force the Meeting Attendes to sign up. Now they basically removed the core feature of the web client without a single fucking word. This must be a joke.


@Tommy @TimZoom, I noticed that the documentation has now been changed to say:

Participants joining through the web client will need to be signed in to a Zoom account.

I am sure you guys are very busy but I for one would really appreciate getting some kind of official response to these sudden and critical changes to your service.

We just bought 100s of zoom meeting and webinar licenses; if this change to how the web client works is going to be permanent, we’re going to have to re-think our investment in Zoom.


We’re in the same boat. Our clients do not want to have to create zoom accounts. That’s the whole point of using the SDK and the API. We need to know ASAP if we should transition to something else, this current option is not tenable.

1 Like

Verified web client seems to be working now when you join using zoom.us/wc/join/{meeting_id}.

However, webSDK is still giving me 403 error. New update ?

It’s definitely not working, it requires you to login. The whole point of the web client was that you didn’t need to login.


The whole point of the web client is not needing to download and install the desktop client. This is important for environments where installing software by the users is impossible. In this regards it is working. Join without login works from the desktop client. What’s not working is joining with no installation and no login.

1 Like

You’re definitely right, that is the point. But the concern is that it seems we will be able to eventually use the WebSDK to run meetings without installation, though it will require people to have Zoom accounts. Regardless, I agree 100% with you.

Just checking in here, everyone. There are lots of moving parts and things are happening very fast. We will provide a more concrete update by the end of Monday 4/6.

I don’t want to give false info on accident or give people false hope. I know this is tough and we’re asking a lot, but if I can ask for some patience we will give you all the details as soon as they are all known.

Thank you for being a Zoom customer!

1 Like

Why does status.zoom.us show a big green “All Systems Operational” when this is not the case? You have a major part of your infrastructure down and have been brushing it away for the last few days.

Seems like, from outside observations, all these actions and changes were done to mitigate the information scraping and leading towards war dialing/zoom bombing.

However with how you have performed the rash actions and with the lack of communication, I now fear we are looking at something much more serious. These actions (or lack thereof) seems to point that you are in a very difficult position and are being told to keep it under wraps by senior leadership and/or legal counsel.

You are eroding the trust of the most influential users you have, the developers. It’s a terrible and rare occurrence to see an entire customer base be put into limbo like this.


status.zoom.us shows the issue as resolved. But it clearly is not.


This is not good enough. You are already giving us false hope and information by stating on your own Zoom status page that everything is operational. We were able to refer our customers to that page so that they realized it’s not our fault (not that it helps in any way), and now that you are displaying false information there as well we have nothing to say.

What a joke and scam.

1 Like

Update: this seems to be due to some old code on our side that set approval_type of 0, but it’s never been a problem until now. This is new behavior Sunday evening, but is fixed by setting the value to 2.

Things are changing under my nose. This is what I get now when trying to send users to join a meeting using the standard join URL (with password embedded):

When continuing, and selecting web client I get this:

… which is not true.

Same issue here, I do keep getting 403 Error on console for the WebSDK

And this is what shows on the view of the WebSDK

I’ve assumed it was working after seeing the status page, but after looking to everyone’s problem here, it seems it’s a misleading page.

I am also facing the same issue

This is unacceptable and unbelievable. We have bought about 50 licenses last week, and are in the middle of a process to switch our whole company to Zoom. Accessing the Web Client without a Zoom Account is a mandatory feature required by our customers. If this is not possible anymore, our work over the last few weeks is wasted. You are forcing us to to cancel all of our Zoom subscriptions to switch to a better solution. Our customers are outraged.

Even worse, the current way of account creation is flawed: As we are using SSO Integration, participants are not forwarded to the Zoom Account Page to create their account, instead they are forwarded to our SSO IDP Provider to login with a SSO account - which is not possible for them!

1 Like

i’m last three days facing same issues. No improvement.

Error : Failed to load resource: the server responded with a status of 403,

“Your connection has timed out and you cannot join the meeting. Verify your network connectivity and try again.”

Anybody knows that, When this issue will solve it ?


We need to be able to simply allow our clients to enter the Zoom meeting from an embedded web page component, this was working fine 3 days ago. bring it back please.

Simple and easy, keep it that way. Forcing clients to redirect to a singin page when clicking on “Join from Browser” is ridiculous, especially if you are sending the wrong message to children under 16 years old who, according to your privacy policy, should not be singing up for an account anyways.

1 Like

How can we get to know when the Web-SDK will be operational?
Your status page (https://status.zoom.us/ ) have no row for websdk.

We’ve been keeping an eye on the problem with the web SDK, which has been bothering us for a few days, but zoom hasn’t had a clear fix or update, which is pretty bad

web sdk still broken for us as well, hopefully it will come back sooner than later