Client error for subaccounts and users

Description
We have a JWT application with api_key and api_secret.
Using api_key and api_secret as well as the JWT token in our application, we faced the problem of starting a meeting for its host as well as getting information on it.

  1. Meeting for a subaccount.Using the zoom API, we create a meeting for the subaccount https://api.zoom.us/v2/accounts/:account_id/users/:user_id/meetings/ As a result, we get a response with information about the created meeting with the assigned id. Using the Meeting SDK in our application, we try to access the scheduled meeting as a host.For this request we generate a signature and pass all the necessary fields such as: apiKey, meetingNumber, passWord as a result of the request we get a response containing the error “Signature is invalid.” With code 3712.

  2. Meeting for users. Using API zoom we create a meeting for a user. https://api.zoom.us/v2/users/:user_id/meetings. As a result, we get a response with information about the created meeting with the assigned id. Using the Meeting SDK in our application, we try to access the scheduled meeting as a host.For this request we generate a signature and pass all the necessary fields such as: apiKey, meetingNumber, passWord as a result of the request we get a response containing the error “Joining meeting timeout. Meeting does not exist…”.

Browser Console Error

Which Web Meeting SDK version?
2.0.1

Meeting SDK Code Snippets

To Reproduce(If applicable)
Steps to reproduce the behavior:

  1. Go to my website with the web client
  2. Clicked the Join meeting button
  3. An error occurred.

Screenshots
If applicable, add screenshots to help explain your problem.

Device (please complete the following information):

  • MacBook Pro (16-inch, 2019)
  • OS: macOS 12.0.1
  • Browser: Chrome
  • Browser Version 96.0.4664.55 (Official Build) (x86_64)

Hey @hitin73

Thanks for reaching out!

In this case, make sure that you are using an API Key and Secret from the sub-account itself. This error seems to indicate the API Key and Secret are incorrect.

Right off the bat I’m not sure what’s wrong here. If you’re able to submit a ticket through our Developer Support Center with a link to this thread I can investigate further using the signature.

Thanks,
Max

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.