Invalid redirect: http://localhost:3000/api/zoom/callback (4,700)

API and Webhooks Authentication
1

I have created a general app (General app 600) and completed the steps and made it localready.

I have generated the below URL, which should take me to the login screen so that the user can authorize the app and receive the access token and the refresh token.

Below is the URL

https://zoom.us/oauth/authorize?response_type=code&client_id=WYzSPWOOT2eakawUm3AWw&redirect_uri=http://localhost:3000/api/zoom/callback

It was working fine until last week but since Monday, it is not redirecting to the login screen and is returning the following error:

{"status":false,"errorCode":4700,"errorMessage":"Invalid redirect url","result":null}

Please resolve this urgently.We are waiting for this.

Thanks & Regards

Srinivas Polishetty

2

@Srinip Hi,

3

Same 4700 here as of August 2026, still broken.

We’re connecting Cursor / Grok Bot to Zoom’s official MCP using a user-managed General app on a business Zoom account. Cursor sends:

redirect_uri=http://localhost:8787/callback

That exact URL is in both the OAuth Redirect URL field and the OAuth Allow List (Development). We also allowlisted https://localhost:8787/callback and https://www.cursor.com/agents/mcp/oauth/callback. Scopes are added. Strict Mode is off.

Authorize still returns:

{"status":false,"errorCode":4700,"errorMessage":"Invalid redirect url","result":null}

This matches the reports that Zoom stopped accepting localhost redirects. Cursor’s MCP desktop/agent flow hardcodes localhost:8787, so we cannot complete Zoom MCP OAuth at all.

Can Zoom confirm whether localhost / loopback redirects are intentionally blocked now, and if there’s a supported path for local MCP clients that must use http://localhost:8787/callback?

4

hi @Srinip , @Patrick12

You cannot do OAuth or callback to Zoom from localhost.

When you use Zoom for any kind of authentication, Zoom needs an external URL to connect to.

If you are testing, then you can use a tool like ngrok to tunnel an external URL.
When you roll out on a server, I expect you will then have an external URL.

This is because the auth goes to Zoom, who will show a page from Marketplace to get approval, and then they need a registered return URL for the Marketplace to connect to.
An external Marketplace App can not connect to your local URL; it is the Marketplace that is trying to connect, not the browser.

I hope that makes things clear.

John