Publishing a Multi-Tenant OAuth General App with No User Interface

App Marketplace
1

Hi Zoom Developer Team,

We are creating a Multi-Tenant OAuth General App whose only purpose is to get customer consent and read Zoom Rooms and Zoom Phone device details using authorized scopes.

The app does not have an actual end-user UI or standalone product interface. It is mainly used for backend integration/device discovery after customer authorization.

While trying to publish the app, the Marketplace submission requires many mandatory items such as:

  • App Icon

  • Cover Image

  • App Gallery screenshots

  • Documentation URL

  • Support URL

  • Landing Page

  • Other details

Since our app is only used for OAuth consent and API access, we want to understand:

  1. Is there a way to publish a Multi-Tenant OAuth app with minimum details?

  2. Are App Gallery screenshots mandatory even if the app has no UI?

  3. Is there any alternative approval process for backend/service integration apps?

  4. What are the minimum required details/documents needed for publishing this type of app?

Our use case is only:

  • Customer installs the app

  • Grants permission

  • We read Zoom Rooms and Zoom Phone device information via APIs

We are not building a customer-facing Marketplace application with rich UI features.

Any guidance or best practices would be appreciated.

Thank you.

2

Hi there,

Thanks for reaching out about publishing your OAuth app.

Based on your use case, an Unlisted App would likely be the best fit. Unlisted apps aren’t searchable on the Marketplace but still allow external customers to authorize and use them.

However, unlisted apps still require all metadata (app icon, cover image, screenshots, documentation URL, support URL, etc.). The listing page is still viewable from their added apps list, and has the same requirements as a published app listing page. The app will fail review without complete metadata.

There’s no reduced-metadata path for backend integrations. For screenshots, we recommend images of your OAuth consent flow or a simple diagram showing how the integration works.

If the app is strictly for internal use within your own account, a Private App bypasses review and metadata requirements entirely, but cannot be used by users outside of your Zoom account.

Full breakdown of distribution types here: Private vs Beta vs Published vs Unlisted Apps

Let me know if you have any further questions.

Thank you,