Error 3712 Invalid signature on join, valid via OAuth/API, started right after upgrading Basic to Pro

Summary: Web Meeting SDK signature is rejected with error 3712 “Invalid signature” when joining a meeting hosted by the same account that owns the app. Confirmed via OAuth that the Client ID and Secret are valid and the app is authorized on the account, so the credentials themselves are not the issue.

App: Client ID MjwaiEtjRAO6vQajDlS43g. General App, User Managed, Development credentials. Meeting SDK feature enabled under Embed, app added to account (Local Test: Ready).

Meeting: number 87163137393. Host is the same user/account that owns the app (verified via GET /v2/meetings/{id}: host_id matches the authorized user).

Error: errorCode 3712, errorMessage “Invalid signature”. Reproduced with the zoom meetingsdk npm package versions 3.11.2 and 6.5.0 (also 6.5.0 without sdkKey in join, per current typings). Same result calling the wc/info endpoint directly with a freshly generated HS256 JWT (appKey/sdkKey, mn, role, iat, exp, tokenExp), so it is not a client rendering issue. tid from one attempt: v=2.0;clid=us06;rid=WEB_840013f28d1f85e678ae6413137b2271, at 2026-09-26 17:05 UTC.

Already ruled out: regenerated the Client Secret and tested with two different General Apps, both with the same result. Tried joining with a valid ZAK for the meeting host, obtained via GET /v2/users/me/zak, still got 3712. Confirmed via OAuth token exchange (POST /oauth/token) that the Client ID/Secret are valid and the app is authorized.

Also checked account settings: the “Manage which Zoom apps can join as a participant” setting is OFF (any SDK app allowed). Marketplace admin Permissions require no approval for published, beta or development apps, and there is no IP allow-list restriction. The meeting itself has no meeting authentication, no waiting room, and join before host is enabled.

I also checked the wc/info returns HTTP 503 thread on this forum, but that is not our case: we get a clean HTTP 200 with a JSON error body, not 503s, so it does not look like a firewall or network block. I also contacted Zoom Support chat (account is Pro, Owner role); they confirmed this needs the developer/engineering team.

Timing: this started right when the account was upgraded from Basic to a paid Pro license. Everything else (app config, credentials, meeting settings) is unchanged from when it worked on Basic.

Question: is there something account-side, not exposed in the admin UI, that blocks Meeting SDK signature validation for newly-Pro accounts, or something specific to General Apps created while the account was Basic that needs re-provisioning after the plan change?

Happy to provide more tids or try anything else needed to debug.

creating an internal ticket for this, will update you when i get more information. thanks for the tracking id
ZSEE-214947

@CarlosT Meeting SDK is not turned on in Embed.