Invalid Redirect URL (4,700) on valid redirect url

API and Webhooks
41

Thanks for the reply @tommy,
I’ve tried changing the “Redirect URL for OAuth” from https://any.melonlearning.com/oauth/zoomauth to my base domain https://melonlearning.com/oauth/zoomauth and whitelisting my new tenant https://melonlmstraining.melonlearning.com , but again I get the 4700 error when trying to initiate the OAuth flow from https://melonlmstraining.melonlearning.com. The original address https://melonlms7.melonlearning.com/ works without any issues.
Note that the https://melonlmstraining.melonlearning.com was whitelisted after the app was published (I tried to Regenerate the Publishable URL, as I’ve read this might help, but it had no effect).
Attaching screenshots of my Whitelist URLs

Whitelist
Whitelist787×488 6.88 KB

and the 4700 error
ZoomOAuth4700
ZoomOAuth47001213×281 12.7 KB

42

Hey @pcvetanov,

Can you try moving your state query param to before the redirect uri? Like this:

authorize_url?client_id=asdfasdf&state=asdf&redirect_uri=https://zoom.us

Let me know if that works! :slight_smile:

Thanks,
Tommy

43

@tommy Can you validate something for me? I was approved last Thursday for using the production install link for beta users until our app submission is approved. I received an email on Friday stating that the submission requires further information to be approved and now a beta user cannot use the install link.

Are we not allowed to use the production install link now that app has to be resubmitted?

I looked at the Submit portion of my app and it appears that my publishable URL should work. So something isn’t making sense

image
image796×437 23.4 KB

The app name is Presence and the redirect uri that I’m using is https://richmond.presence.io/admin/zoomauth which matches and was working last week.

44

Hey @jeffatpresence,

Are you seeing an error / cannot install outside account message when a user is trying to install your app? If so, can you share a screenshot?

Thanks,
Tommy

45

I’m getting the same error mentioned in this thread, invalid redirect 4700. It was worked for awhile and we noticed that it wouldn’t work today. So I was wondering if that was tied to me app being rejected for it’s initial submission.

46

Hey @jeffatpresence,

What is the name of your app? It should not be connected to an app publish rejection.

Thanks,
Tommy

47

My post above has my details. The app name is Presence.

The redirect URL specified in marketplace:
https://any.presence.io/admin/zoomauth

The redirect URL that is not working (and none others are working):
https://zoom.us/oauth/authorize?response_type=code&client_id=<PRODUCTION_ID>&redirect_uri=https://richmond.presence.io/admin/zoomauth

The production client Id was removed but we are using what’s specified in the publishable URL.

48

I’m also getting the same invalid redirect 4700 message. My app, named Continu, has been published for a while and had many subdomain integrations. The only difference I can find with the reported error is that the subdomain is only 2 characters, but I don’t see why that would have any affect.

49

Thanks @michael3, @jeffatpresence,

We believe this to be a bug, and are currently investigating the issue.

-Tommy

1 Like
50

Hey @jeffatpresence, @michael3, @pcvetanov,

It should be fixed now! :slight_smile:

Please try and let me know if you see any issue.

-Tommy

51

Thanks @tommy! This appears to be resolved on my end.

1 Like
52

It’s working for me now as well. Thanks so much for the help!

1 Like
53

Hey @jeffatpresence, @michael3,

You are welcome! Apologies again this happened!

Thanks for building with Zoom! :slight_smile:

-Tommy

54

Hi @tommy,

Thanks for the suggestion - moving the state param outside the redirect_uri did the job and I can now get oauth code and exchange it for an access token. Many thanks once again!

1 Like
55

Great! You are welcome! :slight_smile:

Thanks,
Tommy

56

Hello,

I’ve read this thread because I am having the same issue. I have just added a new Whitelist Url on a Published app, but I’m getting the Invalid Redirect URL when trying to authorize over this new URL.

The last message from @tommy on Aug 11 suggests a bug was fixed, but I am still experiencing the issue. It seems to work with the Development version of the app but not with the Production version.

The app name is: Breeio

Any help would be greatly appreciated.

Kind regards,

Dayo.

57

Hi,

I have found a workaround to the above so this is no longer an issue for me but for reference, please could someone confirm whether it is possible to add new Whitelist Urls to an already published app or if it is necessary to re-submit the app for review after adding new Whitelist Url/s?

Thank you very much,

Dayo.

1 Like
58

Hey @dayo,

Any changes on a published app will take affect immediately on the development credentials, but for the changes to take affect on the production credentials (the published version of your app) you must submit an update request and have it be reviewed and updated.

Thanks,
Tommy

59

Hello,

Thank you very much @tommy for confirming. I didn’t realise at first that changes to the white list urls had to be re-submitted. We no longer need to change them so all’s OK now but it’s good to know.

Kind regards,

Dayo.

1 Like
60

You are welcome! :slight_smile:

Thanks,
Tommy