Apps may be submitted for Public release on the App Marketplace for all users to install. Once you have submitted an app, the Marketplace team will conduct a Submission Review. If successfully approved, your app will be available on a public landing page featuring the app and through an embeddable button for external installation.
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 will allow users on your account to install your app without releasing it publicly.
The Zoom App Marketplace currently only supports English language apps.
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 Install button. This will install the app on your account using the app’s Development credentials. Generate a Testable URL to share a locally developed app.
If an app was previously installed on the Zoom Client, relaunch the Testable URL to uninstall the app.
Note: Locally developed apps can only be tested on the same account which developed the app. The Testable URL will not allow other Zoom accounts to install or test 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.
Choose a unique, simple name (50 char max) which hints at what your app does or use your company name. Avoid generic terms or names which are too similar to existing apps.
Use the Short Description to provide information about your business’s core purpose for customers and explain what your app does in a nutshell. Highlight features or typical use cases of your app. Short descriptions should be 1-2 sentences (max 150 char), 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 install 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. Long Descriptions can be updated when a new version of the app is submitted.
A demo video in your app card is strongly recommended, but not required. Videos (max size 40mb) should help users discover and learn about your app. Remember to not use content which does not belong to you (music, clips, etc).
At least one image or video is required in preview content. Remember to use a high enough resolution to appear clearly on screens of varying sizes. For an example of high-quality image & video content, reference the Panopto Demo on the App Marketplace.
Select a category which best describes the main function and purpose of your app:
If your app has industry vertical-specific compliance like HIPAA or FedRAMP, or is specific to Higher Education or K-12, please also choose the optional vertical that applies: Education, Healthcare, Government. If you do not see the industry vertical specific to your app let us know at email@example.com.
Release Notes for the App Reviewer will help the Marketplace team effectively test your app. It is recommended to be as thorough as possible to provide information on roles needed for permissions and effective functional testing. App submissions without sufficient testing release notes will likely require a resubmission.
If you are upgrading an app, you can provide Release Notes for the App Users. In these notes, include information about any features and/or bug fixes available with the upgraded app. This information will be delivered directly to any app user who has opted to receive transactional emails from the Marketplace.
All published apps are required to provide a Documentation URL to guide users through app installation and usage. When creating documentation, provide the following guidelines:
Installation (Required): A step by step guide for a user to install your app. Link to an installation troubleshooting guide.
Usage (Required): For each feature or action, provide a clear use-case description and a list of any prerequisites.
Uninstallation (Required): A guide to uninstalling the app from your Zoom account. Notify the user the implications of Deauthorization, and how you will remove their data. If your app has specific requirements, be sure to include these. A simple list like the following will suffice, as uninstallation is handled by Zoom:
- Login to your Zoom Account and navigate to the Zoom App Marketplace.
- Click Manage > Installed Apps or search for the XYZ app.
- Click the XYZ app.
- Click Uninstall.
In the above list, we have used “XYZ” as a reference for an app. In your documentation, you should replace it with your app’s name.
Troubleshooting (Optional, but highly recommended): List the most common user issues and their solutions including installation issues, adding meetings, accessing recordings, etc.
FAQ - (Optional): List the most frequently asked questions, including questions on authorization, activation emails, or unsubscribing to email updates.
Contact Support (Optional): Describe what users can expect when engaging your support team including the hours of your support team and first response SLA (maximum time a user should expect to wait to hear from your support team). Provide a link to create a support case or contact support through email, KB/Forums, or phone.
All published apps are also required to provide a Support URL for individual on-going support for users. While the Marketplace provides active support for use of the platform, all apps are required to provide users with their own dedicated support options.
Describe what users can expect when engaging your support team including the hours of your support team and first response SLA (maximum time a user should expect to wait to hear from your support team). Provide a link to create a support case or contact support through email, KB/Forums, or phone.
Any domains receiving callbacks or requests from Zoom must be authorized. To verify a domain, download the HTML file with a verification code and place the file in a folder called
/zoomverify under the root of the domain. Once this is completed, click Validate to allow the app to be submitted for review.
Test Account and Credentials
Your submission must include a designated test account and credentials to support the Marketplace review team in functional and usability testing. If an account is not required to login to your app, select No account required. If a trial account is required, provide a Free Trial URL. Select Login Page URL to provide the login page along with a test username and password.
App Approval & Removal
When an app has been approved, the Marketplace team will notify you of successful approval and public availability of the app. From this point, any Zoom user will be able to install your app using production credentials.
For more information on this process, reference the Submission Review guide.
To remove an app from the Zoom Marketplace, navigate to the My Apps section of the Marketplace. If the app has not yet been published, the app can be removed directly. If the app has been published, choose the change icon and select the option to Remove. Further status updates will be provided by email.