We are developing an integration between Zoom and our own web service.
The integration consists of three Zoom applications:
- Account-level REST application: to allow users to create meetings
- User-level REST application: to authorize users in Zoom to get their account information to create meetings (by the Account-level REST application) with the right host
- Web SDK-based application which is used to run the created meetings
So, the user flow is the following:
- an administrator installs the Account-level REST application and sets up the integration
- each user (in our web service) who has an intention to run meetings should authorize in Zoom using its credentials (the user-level REST application)
- when a user tries to create a meeting, it is created by the Account-level application, but using the actual Zoom user as a host (we got this info from the previous step)
- all participants (including the host) use the Web SDK application to join the meeting anonymously (as Web SDK doesn’t support OAuth)
To make all this work we need to have publishable URLs for the Account-level and User-level applications, but actually they should be installed from our web service. I think it is better to have only the Account-level application published in the Zoom marketplace, but it should lead to our own marketplace.
So, my questions are:
- Are there any suggestions on how to make the scheme easier?
- How can we get publishable URLs without actual listing in the Zoom marketplace?
- Can we lead users to our own marketplace from your one?