Looking for:
– Prerequisites
Here admins can either install the app or reject the request. Clicking Uninstall will prompt a confirmation to remove the app. If you’re looking for help, try Developer Support or our Developer Forum.
Priority support is also available with Premier Developer Support plans. End User Authorization Flows The Zoom App Marketplace lists all publicly available apps which can be installed by individual users or accounts User-managed or Account-level apps. A sample pre-approval request flow for an end-user is shown below: Pre-approval request flow on the User’s end Make pre-approval request After requesting pre-approval After admin grants pre-approval Pre-approval request processing for Admins Admins can manage pre-approval requests made by users by navigating to App Requests in the My Admin Dashboard.
Select an app for pre-approval. Enable the Pre-approve option. Only the users whose emails are added will be able to install this app. Note: Changing this setting does not affect existing subscriptions. If approved, your app will be available on a public landing page featuring the app and through an embeddable button for all users to add.
Fill out this form prior to submitting your app so that you can assess your app in its current state. Once you complete the assessment, you will receive an email with a link to an auto-generated App Review Report highlighting existing issues and recommendations on how to resolve those issues.
Creating a private app allows users on your account to add your app without releasing it publicly. It is highly recommended you test your app locally before submitting for approval. To authorize a local test, navigate to Local Test and click the Add button.
Generate a Testable URL to share a locally developed app. Note: Locally developed apps can only be tested on the same account which developed the app. Your app listing is a public landing page for users on the App Marketplace. Use this section to tell users what your app does for them, how it works, and how to get started. Include features, benefits, and any information which would help readers decide if your app provides value or solves their problem.
Zoom reserves the right to remove or require a revision to any content, in whole or part, including an app name, that violates these Requirements, the Marketplace Developer Agreement, the Zoom Terms of Service, our Community Standards, or for any other reason at our sole discretion.
Highlight features or typical use cases of your app. Short descriptions should be sentences a maximum of characters , and can be updated when submitting new versions. Provide a Long Description which highlights the features of your app. Use this section to describe your App as a service, and your company as an organization.
This is your opportunity to tell Zoom users why they should add this integration, what value does your app provide, and why your app is the right solution for them. Ideal descriptions contain a concise, informative paragraph followed by a short list of main features.
Long Descriptions can commonly cause an app submission to be denied if it lacks sufficient information about app functionality. An example of an admin-added app could be an app that analyzes meeting participation reports or helps manage all webinars on an account.
Your app is unlikely to require Sub-Account permissions unless it is intended to be used by API Partners , and may be denied if they are not required. To release onto the Marketplace, all public apps must undergo a dedicated Submission Review process for information and functional review.
Once an app has been submitted, the Marketplace team will conduct this review independently, but work directly with you on any additional requirements. Once an app has been submitted, the Marketplace team performs a Security Audit and Penetration Test focused on maintaining security and resilience as well as protecting customer data.
More details on security testing can be found in our Submission Review guide. All published apps are also required to provide individual on-going support for users. While the Zoom Marketplace provides active support for the use of the platform, all apps are required to actively provide users with their own dedicated support options.
Webhook-only apps use Event Subscriptions to integrate and connect third-party services to the Zoom platform when an action event is triggered. This allows you to automate the task of being notified when a certain event occurs in your Zoom account without making repeated API calls. This could allow your application could to send data to your server when a new User or Meeting is created, store recorded data when a Meeting Cloud Recording has ended, or enable Deauthorization events to notify your database when a user uninstalls your app.
For a full look into Webhook-only apps, read our Webhook reference. Zoom SDKs provide a rich-set of Zoom client-side functionality that can be integrated into your native apps.
Currently, with our SDKs, we offer video-conferencing features that mirror the meeting experience in the Zoom Client. We offer SDKs that are compatible with various languages, platforms, and frameworks.
It supports iOS 8 and later versions. It supports Windows XP and later versions. It supports MacOS By integrating the Web SDK in your web applications, you can enable meeting features that are available in the official Zoom Web Client. These features include allowing users to join meetings either directly from your app or by dialing in from their phones, send and receive screen-share from other attendees during the meeting and leave the meeting.
If you’re looking for help, try Developer Support or our Developer Forum. Priority support is also available with Premier Developer Support plans.
Zoom app marketplace permissions
This scope allows an app to an account’s H. Only the users whose emails are added will be able to install this app.