OAuth Guide
← All guides

Zoom

Hard

A General (OAuth) app works in your own Zoom account within minutes, but outside your account you either need Zoom's approval to share a beta app (capped at 10 account-level or 100 user-level installs, with URLs that expire after 4 weeks) or you must publish through Marketplace review, which includes a functional review and a security review with technical design documentation and OWASP testing.

Agent-researched, not yet reviewed by a personResearched 2026-10-20

Working in dev

15–60 min

Signing in with your own account

Any user can connect

2–6 weeks

A published Marketplace app (can be unlisted via 'install from your landing page') that reads meetings, recordings or transcripts for any Zoom user; a beta share to up to 100 external users takes 3–4 business days. Zoom's docs give no review timeline; remediation rounds can push it to 8 weeks or more, as forum reports describe.

Waiting on
Marketplace functional review, then security review (technical design document review, scope evaluation, OWASP testing), plus any remediation rounds.
Cost
Free to build and submit; no review fee found. API rate limits depend on the customer's Zoom plan (Free accounts have low daily caps).

What you need first

  • A Zoom account with permission to create Marketplace apps

    Apps are created in the Marketplace developer console and tested by installing into your own account.

  • Public HTTPS redirect URL and an allow-list entry for it

    The OAuth flow returns the code to your registered redirect URL.

  • For publishing: technical design documentation, security information, clear listing content, and a test plan

    The submission completeness check and security review depend on them, and unclear scopes or listings lengthen review.

Who does what

Zoom OAuth setup · OAuth Guide