OAuth Readiness
Back to all apps

Zoom

Generated live by the research agent (Gemini), checked 2026-10-19. Setup not tested by hand.

Building a public OAuth app on Zoom requires registering an application on the Zoom App Marketplace and implementing standard OAuth 2.0 authorization flows. Public apps must then pass a thorough Marketplace submission review process covering metadata, functionality, and a security audit.

Not enough evidence to rate

Hands-on work
0+ hours
Waiting for approval
Unknown
Confidence
low

Assumes: A public OAuth app that external Zoom users can connect to, requesting standard user scopes for an AI agent to read and act on user data.

The agent couldn’t establish 4 of the 7 facts that set difficulty, so it won’t guess a tier. Known hurdles put it at tier 4 or higher. Check the provider’s developer docs directly, or regenerate later.

10 min1 hour1 workday1 week1 month6 months

Solid dark bar: your hands-on work. Amber: the minimum wait. Hatched: the range sources disagree on, or an open-ended wait. (no source)

Biggest blocker: The requirement to pass a comprehensive App Submission Review and Security Audit by the Marketplace Operations and Security teams.[2]

Recurring: All developers are required to provide individual on-going support to users for their published apps, including a Support URL, Terms of Use, Privacy Policy, and Self-Serve Documentation.[2]

What we know so far. Set by: security assessment. 4 facts unknown, so the tier could be higher.
The tier is computed from these seven facts by a fixed rule, not chosen by the AI. Low: some facts are unknown or rest on forum reports. Verify before you plan around this.
Self-serve credentialsYesDevelopers can create and set up OAuth apps directly on the Zoom App Marketplace.[3]
Limits until reviewedUnknownThe sources do not specify particular connection caps or dev mode token limit details for unreviewed apps. (no source)
Provider reviewYesExternal Zoom users can discover and install your app from the Zoom App Marketplace after it passes Zoom's review process.[2]
Security assessmentYesThe Marketplace Security team performs a Security Audit and a focused security test on Zoom scopes.[2]
Business verificationUnknownBusiness verification details are not mentioned in the provided official documentation. (no source)
Mandatory feesUnknownFees for app submission or review are not stated in the source text. (no source)
Partner or paid accessUnknownThe sources do not mention whether a partner program or waitlist is required for app submission. (no source)

You can start today without any of this. Composio already provides a managed OAuth app for Zoom (zoom, zoom_chat, zoominfo), so users can connect while you work through your own app. You need your own app for your brand on the consent screen, your own rate limits, or scopes beyond the defaults. Managed auth list

If your case is different

Unlisted apps
Unlisted apps might be a preferable option if you want to limit access to your app and don't want it available to the general public.
Internal apps
Apps intended for users within your own Zoom account are intended for internal use and don't require the standard Marketplace review.

Steps

Agent steps an AI agent can do or draft for you. You steps that need your identity, accounts, legal authority or a real demo.

  1. Create an OAuth app

    You

    Create an OAuth app on the Zoom App Marketplace to get started.[3]

  2. Implement OAuth 2.0 authorization flows

    Agent

    Follow the OAuth 2.0 authorization documentation to handle token exchanges, requests, and refreshes.[1][3]

  3. Prepare support and policy documentation

    You

    Provide at minimum a Terms of Use, Privacy Policy, Self-Serve Documentation, and Support URL.[2]

  4. Submit app for review

    You

    Submit the public app to undergo the dedicated App Submission Review process for metadata, usability, compliance, and security testing.[2]

What you will need

  • Terms of Use[2]
  • Privacy Policy[2]
  • Self-Serve Documentation[2]
  • Support URL[2]

Nuances that catch people out

  • Access tokens expire after one hour and require using the refresh flow to obtain new ones.[1]
  • If it is the user's first time authorizing your app, or if scopes or webhook settings are updated, Zoom prompts the user to authorize again.[1]

Evidence

What we could not verify

  • Exact hands-on development hours required to implement the integration.
  • Specific calendar wait times for the Marketplace review process.
  • Any applicable review fees or business verification requirements.

Sources

Each quote was checked by code against the live page. “Not found on page” means the quote may be paraphrased, so treat that claim with care.

  1. OAuth 2.0 - Integrations - Zoom Developer Docs
    Provider docsQuote found on pagechecked 2026-10-19
    Access tokens expire after one hour.
  2. App distribution - Distribute - Zoom Developer Docs
    Provider docsQuote found on pagechecked 2026-10-19
    External Zoom users can discover and install your app from the Zoom App Marketplace after it passes Zoom's review process.
  3. Integrations (OAuth apps) - Integrations - Zoom Developer Docs
    Provider docsQuote found on pagechecked 2026-10-19
    To get started, create an OAuth app on the Zoom App Marketplace.