Join.zoom.us meeting id – none:
These roles are actively involved in the process of authentication with Zoom APIs:. Generally, the interaction between a Client your app , a Zoom user, Zoom’s authorization server, and the Zoom API follows the flow in the diagram below.
An Authorization Grant is the authorization assigned to the Client by the resource owner. The grant type refers to the method the Client uses to request authorization. The usage of this grant type is described in detail in the OAuth with Zoom guide. The following steps provide an overview of the Authorization Code grant flow:. Example Node. The Client Credentials grant is used to get an access token for APIs that require only a service’s permission.
This grant does not require a user’s permission. To use Client Credentials grant type, perform the following steps:. JWTs contain a signed payload that helps establish server-to-server authentication. If only you or your Zoom account users will use your app, it is recommended that you use JWT authentication. The complete URL varies depending on the accessed resource. You do not need scopes for JWT apps.
Your JWT app will only have access to your Zoom account’s information. You can also use the me keyword instead of the userId value. To get information about a user with a user-level OAuth app, the app must have the user:read scope.
While the URL for the request is the same, the behavior of userId value is different from an account-level apps. Instead of providing a user’s userId or email address, you must use the me keyword as the value of the userId path parameter. Otherwise, your app will receive an invalid token error. Server-to-Server OAuth apps also use scopes. You wouldn’t use the me keyword with this app type; you must provide a userId or email address.
See Server-to-Server authentication for details. You can use the me keyword in place of the userId keyword in any supported API call. When you use the me keyword, the API call uses the authenticated user’s access token. Some users may have permissions to access create, read, update, or delete information associated with other users on Zoom accounts. For example, the Schedule Privilege enables users to assign other users on their account to schedule meetings on their behalf.
A user that has been granted this privilege has access to schedule meetings for the other user. A user may also have a role that grants them access to other user information. With shared access permissions, a user can choose whether your app can access the following information:. Item 2 refers to when a user authorizes your app to use their “shared access permissions” after they add or manage your app on their account.
In the example above, the user can choose to share access permissions to schedule meetings for another user’s account with your app. See Allowing Apps access to shared access permissions for details on the end user experience. Your app does not need to do anything different for this access. We have checked with the meeting creation API from the backend and we got success response on both video call as well as audio call.
The audio call is working as expected in SDK. Just for info this account it was already activated and verified from zoom Note: It is live account so please fix as soon as possible. This is because you are using a Personal Meeting ID. I have attached that screenshot below. We are just creating the basic flow of creating a meeting by using the below input params. Thank you for providing additional information. I would also make sure that the setting is disabled at the account-level.
Please check the below attached image clearly.
Server-to-Server OAuth apps also use scopes. When you use the me keyword, the API call uses the authenticated user’s access token.