Invalid redirect (4,700) on Production credentials, "Add app now" button is disabled

API and Webhooks
1

App type: General app (User-managed)
App name: General app 806
Client ID: PtxcP5n_TNq0j8JHRbeLHA
Registered OAuth Redirect URL (Production): https://timerex-clone-app.vercel.app/api/auth/zoom/callback

Same URL is also added to the OAuth Allow List.
Development credentials work fine with the same code.
Production credentials return “Invalid redirect (4,700)” even when using Zoom’s own generated OAuth URL (from the “Copy authorization URL to share” link).

The “Add app now” option under the Beta Test dropdown is grayed out and shows no tooltip explaining why.

Scopes (meeting:write:meeting, user:read:user) are configured for Production.

Waited over an hour with no change.

Could you please check the account/app status on your side?

2

It has been over two weeks with no response. This is blocking our production launch.

Additional detail: The “Add app now” option under the Beta Test dropdown remains grayed out with no tooltip explaining why, even after re-saving all OAuth settings and scopes multiple times. Could a staff member please take a look?

3

@kei development is using localhost and this is not a support url unless you turn on device auth and point it to 127.0.0.1

For the missing add app now in production, you are missing these fields

image
image783×287 22.3 KB

4

Thank you for the response. I’ve completed the missing fields you mentioned:

  • Developer Contact Information (Name, Email) under Basic Information
  • Scope description under Scopes

However, I’m still getting “You cannot authorize General app 806” / invalid redirect URL when attempting to authorize with Production credentials via the actual OAuth flow (not just “Add app now”). The registered Production Redirect URL still matches exactly: timerex-clone-app [dot] vercel [dot] app/api/auth/zoom/callback

Could there be another missing requirement, or is this a caching/propagation issue on Zoom’s end?

5

@kei your development oauth url is still localhost. could you change that to some other domain name?

6

Thank you for the earlier guidance. I’ve addressed all the items you pointed out, but the issue is still not resolved. Here’s a full status update:

Completed since your last reply:

  • Basic Information → Developer Contact Information (Name/Email): filled in
  • Scopes → Scope description: filled in
  • App Listing → Marketplace Category and Industry Vertical: filled in (previously missing)
  • Development OAuth Redirect URL: updated from localhost to the production URL
  • Ran “Add app now” successfully — the app now shows the “Share this app” screen (Share within your account: Active)

Still failing:
Despite all of the above, attempting the actual OAuth authorization flow on Production credentials still returns:

You cannot authorize General app 806
無効なリダイレクト URL です。(Invalid redirect URL)

Current configuration (verified multiple times, character by character):

  • App type: General app (User-managed)
  • Client ID: PtxcP5n_TNq0j8JHRbeLHA
  • OAuth Redirect URL (Production): https://timerex-clone-app.vercel.app/api/auth/zoom/callback
  • Same URL is also present in the OAuth Allow List
  • The actual redirect_uri sent in the authorization request (confirmed from the browser address bar) matches exactly:
    https://marketplace.zoom.us/v2/authorize?client_id=PtxcP5n_TNq0j8JHRbeLHA&response_type=code&redirect_uri=https%3A%2F%2Ftimerex-clone-app.vercel.app%2Fapi%2Fauth%2Fzoom%2Fcallback&state=...

Development credentials with the identical redirect URL logic continue to work fine — only Production fails.

Given that every configuration item has now been verified and corrected, and the error persists even via Zoom’s own generated authorization URL, this looks like it may be an issue on the Production app activation/propagation side rather than my app configuration. Could you please check the account/app status again?

Thank you for your continued help.

7

@kei you should be able to move forward now. It was necessary to regenerate the URL on the development side before the update was propagated. Please let me know if there is still issue.