Hello Zoom Team,
I have key question in order to proceed with my task.
Format Your New Topic as Follows:
API Endpoint(s) and/or Zoom API Event(s)
[Link the API endpoint(s) and/orZoom API Event(s) you’re working with to help give context.]
Description
I am using zoom corporate account and my role is Member role. I am working as developer. We have website where we want our customers (who are recruiters) to be able to create zoom meeting from our website and share meeting link with candidate for interview purpose.
So far, I have created OAuth account level APP in the zoom marketplace. It is not published currently. I have created API in my application to create meeting link using bearer token
Error?
I have couple of questions:
-
Let’s app is approved and publish in the zoom marketplace. Is it possible for our website users (who are not a part of corporate account - they are external users) to create a meeting link using zoom API where in I pass website user’s zoom email address in {userid} parameters in this API: /users/{userId}/meetings
-
We currently have business account with zoom. Account is vohraphysicians.com. In that case, is there any limit on number of meeting can be created using API and is there any restriction on meeting duration?
-
How much time approximate it will take to approve app and publish it by zoom team provided that there is no queries raised from zoom team?
-
Since we have business account with zoom, can we get in touch with zoom representative in order to resolve any blockers quickly?
-
During processing of obtaining authorization code by using call back URL, zoom is asking to enter user name and password. We do not want our customers/users to enter zoom credentials while creating a meeting through our website. Is there anyway to skip this step by doing it through back end API OR using single sign on zoom automatically verifies it if we provide user’s zoom account email address in someway?
I would really appreciate if you can provide answers as early as possible? It is kind of urgent request.
Thank you,
Hardik