OAuth Setup Guides

How hard is it to get an OAuth app approved?

Look up an app to see the likely time, effort and blockers, what an agent can do for you, and where you take over. Every claim says how we know it.

Library

Asana3/5 · limited evidence

Internal or test use needs no review; only apps going to other workspaces or the public app directory go through review, which Asana aims to answer within one week (longer for app-component apps).

Generated live
GitHub1/5 · self serve

Self-serve and fast for a personal or org-owned OAuth app: the docs we read describe no app review, verification or fee, so registration is a form you can fill in today; the real friction is organization-level OAuth app access restrictions, which are on by default for new orgs and need an owner to approve.

Generated live
Google (Gmail)4/5 · heavy review

Testing is same-day and self-serve, but any public Gmail integration needs Google OAuth app verification: 3-5 business days for sensitive scopes, and several weeks plus a paid third-party security assessment for restricted scopes, repeated annually.

Generated live
HubSpot1/5 · self serve

One route: create a legacy public app in a developer account, set the redirect URI and scopes, and install it with a Super Admin — the docs we read describe no review, fee or verification step, but they also never quantify any approval wait.

Generated live
Linear1/5 · self serve

Self-serve: register the OAuth app in your Linear workspace and set redirect URIs in minutes; the docs we read describe no review, fee or verification step, so the main work is deciding private vs. installable distribution and getting the app details right.

Generated live
LinkedIn5/5 · partner gated

Open Permissions (profile, email, w_member_social) are self-serve in the Developer Portal; anything beyond that needs a LinkedIn product or partner approval, and restricted Marketing APIs are evaluated case-by-case with no fixed timeline.

Generated live
Microsoft Outlook5/5 · partner gated

Self-serve app registration takes minutes, but a public multitenant app that asks for more than basic sign-in needs publisher verification, which requires a verified Microsoft AI Cloud Partner Program account, a non-onmicrosoft.com publisher domain, MFA and specific admin roles — and the docs we read describe no app review or security assessment.

Generated live
Notion3/5 · limited evidence

Public connections must be submitted for review before the Authorization URL is populated; internal connections and personal access tokens skip that review, and the docs we read describe no business verification, security assessment or fee.

Generated live
Shopify3/5 · limited evidence

Custom-distribution apps need no Shopify approval; public App Store distribution requires a full App Approval submission and a 100-checkpoint review, and the choice is permanent once made.

Generated live
Slack4/5 · heavy review

Single-workspace install is self-serve and quick; reaching other workspaces means either unlisted distribution (no review described) or Slack Marketplace listing, which adds a security review and scope review with no published turnaround time.

Generated live
X (Twitter)2/5 · light review

Sign up at console.x.com, create an app, enable OAuth 2.0 and register an exact-match callback URL; the docs we read describe no app review, verification or security audit, but X API v2 is pay-per-usage with credit-based pricing and no subscriptions.

Generated live
Zoom4/5 · heavy review

Internal-only Zoom apps skip Marketplace review; anything public goes through a two-phase review (Marketplace Operations, then a Security Audit) with no published wait time.

Generated live