Getting error 200 (No Permission) with new Webclient


Hi everyone,

I am trying to use the WebClient but for some reason this is not working… 


I followed the documentation I found here: .

I did:

  • Ran  npm install
  • Using my own  API Key / API Secret
  • Ran  http-server
  • Created a meeting from the Zoom Client
  • Opened the browser on
  • Copy pasted the meeting number, added a name, and pressed join.

And in the console I can find this (in the requests tab):

{status: false, errorCode: 200, errorMessage: “No permission”, result: null, method: “join”}

What did I do wrong?

Remark: The request seems to be a get (I thought it should be a post). I use the URL generated (copy-pasted from the requests tab in the console) and past it in the URL field in Chrome, I get a full JSON back.

Remark 2: I am using the Zoommtg.generateSignature, I didn’t write my own


Thanks !


Anyone ?


Hi Pierre,

Please make sure you generate the correct Signature before join a meeting.




Hi Wei,


Thank you for your answer.

Here is how I generate my signature:

var signature = ZoomMtg.generateSignature({
  meetingNumber: meeting\_number,
  apiKey: API\_KEY,
  apiSecret: API\_SECRET,
  role: 0,
  success: o =\> {


Do you see anything wrong?


Hi Pierre,

Thank you for your feedback.

Can you provide the meeting number and when you joined the meeting via SDK?

We will check this issue.



Hi Eason,

Below is a screenshot of a test I just did. You can see that one of the console log contains the exact date printed when I tried and the meeting number associated.

Thanks !


Hey, any chance to look at it ?


Thank you,


Hi Pierre,

We found that the signature time stamp is invalid, and please change your PC timezone to UTC and try again.

If failed again, please send the screenshot to me. Thanks!


Hi Eason,

I have the same issue, screenshot attached:


So is it simply the generateSignature doing something wrong ?


Hi Pierre,

Sorry for late reply.

Actually, it’s really caused by wrong signature and time stamp is invalid. Strangely, others has no this issue with the same method.

We recommend that you use the following method in GitHub firstly,

Now we haven’t publish the js method and maybe it still has some problems.

Then we will have a double check and fix it ASAP.