Our application integrates the Zoom Web Meeting SDK into our platform (vidivent). Users normally join meetings through our platform without being authenticated Zoom users. This setup has been working reliably for a long time.
On March 9, 2026 from approximately 09:00 CET until March 10, 2026 around 09:00 CET (which corresponds to March 9, 2026 08:00 UTC until March 10, 2026 08:00 UTC) users were suddenly unable to join meetings. The SDK returned error 4012 (“Only authenticated users can join”).
Since then, the integration has started working again without any further changes on our side.
Because of the recent policy changes regarding automated or AI users joining meetings, we submitted a request for an exception to allow anonymous users for our app. We updated our app configuration accordingly and submitted it for review, but the request is still in the review process and has not yet been approved.
Marketplace ID to our app: rvwBGnMXQoKxY4iBY9XCBw
Our submitted exception request description was:
Vidivent provides business customers with dedicated instances of their web applications. These web platforms support online events and webinars, allowing end users to register or participate anonymously. The platform integrates with various streaming services, including Zoom rooms, where users can log in directly from within the platform. Vidivent passes user data to the plugin, ensuring that participants only need to provide their first and last names, without the need for a Zoom account. Our company is committed to delivering seamless and secure online event experiences for businesses and their customers.
Looking into the OBF FAQ, neither the usage of OBF tokens (host does not need to be inside the meeting room), nor the usage of ZAK token (not all users have Zoom accounts) is viable for our use case.
The reason is that our platform hosts events with many participants who register or join through our platform and typically do not have Zoom accounts. Therefore, requiring ZAK tokens or implementing the OBF host verification flow would not be feasible for our use case.
We are therefore unsure whether the temporary failure was related to the new restrictions or to the ongoing review of our exception request.
Browser Console Error
errorCode: 4012
Message indicating that only authenticated users are allowed to join the meeting.
Which Web Meeting SDK version?
Tested with:
5.10
5.14
Both versions are currently working again.
Meeting SDK Code Snippets
We are currently using the JWT signature approach and have not implemented the Host Verify / OBF flow.
To Reproduce
Observed timeline:
-
Integration worked normally before ~09:00 CET on March 9, 2026
-
From March 9, 2026 09:00 CET (08:00 UTC) until March 10, 2026 09:00 CET (08:00 UTC) users received error 4012
-
After that the integration started working again without further changes
Troubleshooting Routes
We attempted the following:
-
Verified signature generation
-
Upgraded SDK from 5.10 → 5.14
-
Tested multiple meetings and users
-
Confirmed our anonymous user exception request is still pending review
Additional Context
Our customers run scheduled online learning events through this integration. Therefore, it is important for us to understand:
-
whether this temporary enforcement was related to the new anonymous / automated user restrictions
-
whether similar disruptions can occur while our exception request is still under review
-
or whether another factor may have caused this temporary restriction.
Any clarification would help us determine whether our current integration approach remains reliable for production use.