# "invalid session key" error on client.join() **URL:** \ **Category:** Web\ **Tags:** video-sdk\ **Created:** [July 29, 2023, 7:44am UTC](https://devforum.zoom.us/t/invalid-session-key-error-on-client-join/92600 "2023-07-29T07:44:37Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![simonebacchini91](https://avatars.discourse-cdn.com/v4/letter/s/67e7ee/32.png) [@simonebacchini91](https://devforum.zoom.us/u/simonebacchini91)\ **Post date:** [July 29, 2023, 7:44am UTC](https://devforum.zoom.us/t/invalid-session-key-error-on-client-join/92600/1 "2023-07-29T07:44:37Z")
**Description** My app built on the Zoom Video SDK (web) was succesfully running since months, but from yesterday the method client.join() started returning an error 200 “invalid session key”, for every partecipant (host and guests). Nothing has changed in the code, so my guess is that the issue is on the Zoom side. **Browser Console Error** The method join() fails returning: ```auto errorCode: 200 reason: "invalid session key" type: "JOIN_MEETING_FAILED" ``` The request to `https://zoom.us/wc/lsdk?...` fails returning: ```auto zoomsdkjsonpcallback1({ "status": false, "errorCode": 3000, "errorMessage": "invalid session key" }) ``` **Which Web Video SDK version?** “@zoom1234/videosdk”: “^1.5.5” **Video SDK Code Snippets** client.join(sessionName, zoomToken, displayName, “”, 0) **Troubleshooting Routes** I’ve tried the following with no success (same error): - upgrade the client library to the latest version - remove the session key from the JWT (since it’s optional) **Device (please complete the following information):** - Device: Lenovo Thinkpad P15v - OS: Windows 10 - Browser: Chrome - Browser Version: Version 115.0.5790.110 (Official Build) (64-bit) ---
**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\ **Post date:** [July 31, 2023, 2:05am UTC](https://devforum.zoom.us/t/invalid-session-key-error-on-client-join/92600/2 "2023-07-31T02:05:14Z")
Hey @simonebacchini91 Thanks for your feedback. Could you share the value of `x-zm-trackingid` field in the `wc/lsdk` response headers when the issue occurs again? It’s very helpful for us to investigate the root cause. Thanks Vic ---
**Author:** ![simonebacchini91](https://avatars.discourse-cdn.com/v4/letter/s/67e7ee/32.png) [@simonebacchini91](https://devforum.zoom.us/u/simonebacchini91)\ **Post date:** [July 31, 2023, 6:03am UTC](https://devforum.zoom.us/t/invalid-session-key-error-on-client-join/92600/3 "2023-07-31T06:03:04Z")
Hi Vic, thanks for the support. The value of the header is: `v=2.0;clid=us06;rid=WEB_df7deb21ec74bb277e81b3e021c6218e`. Simone ---
**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\ **Post date:** [July 31, 2023, 6:53am UTC](https://devforum.zoom.us/t/invalid-session-key-error-on-client-join/92600/4 "2023-07-31T06:53:20Z")
Hey @simonebacchini91 Got it. We are investigating the issue. We will keep you informed if there’s any update. Thanks Vic ---
**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\ **Post date:** [July 31, 2023, 7:25am UTC](https://devforum.zoom.us/t/invalid-session-key-error-on-client-join/92600/5 "2023-07-31T07:25:10Z")
Hey @simonebacchini91 We found the host started the session with `session_key` field in the JWT payload set, the value is ‘56d0\*\*\*\*70db6’ (Masked the middle part). Could you check it again on the host call? Thanks Vic ---
**Author:** ![simonebacchini91](https://avatars.discourse-cdn.com/v4/letter/s/67e7ee/32.png) [@simonebacchini91](https://devforum.zoom.us/u/simonebacchini91)\ **Post date:** [July 31, 2023, 8:22am UTC](https://devforum.zoom.us/t/invalid-session-key-error-on-client-join/92600/6 "2023-07-31T08:22:03Z")
Hi Vic, the `session_key` value for the session I tried to start this morning (that I used to report you the `x-zm-trackingid` value) is “b8c2\*\*\*76054”. The session key you are talking about is the one from the last session performed succesfully on July 26th. After that we were no longer able to start any call (the .join() method fails). Simone ---
**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\ **Post date:** [July 31, 2023, 9:14am UTC](https://devforum.zoom.us/t/invalid-session-key-error-on-client-join/92600/7 "2023-07-31T09:14:13Z")
Hey @simonebacchini91 Could you check whether the same topic uses the same `session_key` if the field is set? If not, the server will return `invalid session key` error. Thanks Vic ---
**Author:** ![simonebacchini91](https://avatars.discourse-cdn.com/v4/letter/s/67e7ee/32.png) [@simonebacchini91](https://devforum.zoom.us/u/simonebacchini91)\ **Post date:** [July 31, 2023, 9:26am UTC](https://devforum.zoom.us/t/invalid-session-key-error-on-client-join/92600/8 "2023-07-31T09:26:29Z")
Hi Vic, the method `join` wants a token as an argument: I’ve parsed that token (that is a JWT) for each partecipant and I confirm that the `session_key` is the same. The `topic` we are using can be the same string for different sessions too, the unique identifier is the `session_key`. The thing is that also the host can’t start the meeting, even if it is the only participant. Thanks for the support, it is really helpful as the service is running in production, and this issue is blocking. Simone ---
**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\ **Post date:** [July 31, 2023, 10:13am UTC](https://devforum.zoom.us/t/invalid-session-key-error-on-client-join/92600/9 "2023-07-31T10:13:07Z")
Hey @simonebacchini91 There may be some misunderstandings about the `session_key`. `session_key` can not be the unique identifier for the same topic. That means if a host already started a session with `topic` “example1” and `session_key` “keyA”, there’s no longer to start a new session with the same `topic` “example1” and `session_key` “KeyB” or other value until the last session ended. > **[Authorization](https://developers.zoom.us/docs/video-sdk/auth/#payload)** > > The Zoom Developer Platform is an open platform that allows third-party developers to build applications and integrations upon Zoom’s video-first unified communications platform. Thanks Vic ---
**Author:** ![simonebacchini91](https://avatars.discourse-cdn.com/v4/letter/s/67e7ee/32.png) [@simonebacchini91](https://devforum.zoom.us/u/simonebacchini91)\ **Post date:** [July 31, 2023, 12:11pm UTC](https://devforum.zoom.us/t/invalid-session-key-error-on-client-join/92600/10 "2023-07-31T12:11:15Z")
Ok now it’s clear. We are using the same string as a topic for an entire class of (different) sessions, I guess we’ve reached some kind of limit? Now I create a unique topic for each session, and everything is working. Thanks a lot for helping! Best regards, Simone ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\ **Post date:** [August 30, 2023, 10:11pm UTC](https://devforum.zoom.us/t/invalid-session-key-error-on-client-join/92600/11 "2023-08-30T22:11:25Z")
Closed on August 30, 2023, 10:11pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.