Invalid redirect url (4,700) when connecting Zoom

Description
I’m in the process of publishing our app to the marketplace and I’ve setup the publishable url to connect my Zoom account and it works fine when I use the development credentials. When I try to use the production credentials however, I receive the “Invalid redirect url (4,700)” error. I’ve triple-checked the credentials, added the url to the whitelist and no luck. If you’re already logged into your Zoom account then it also works.

I also use state in the url but removing it makes no difference.

Error
Invalid redirect url (4,700)

Which App Type (OAuth / Chatbot / JWT / Webhook)?
OAuth

Thank you.
Kevin.

Hey @kevin2,

What is your app name?

Thanks,
Tommy

It’s TeamLinkt.

With more testing, the issue isn’t just with the production credentials. We have several development environments using different subdomains and even with the development credentials only one of them works and the rest get the invalid redirect url error. I’ve added them all to the whitelist but it doesn’t work. If you’re already logged into the Zoom account then it works.

On a side note, I recently upgraded our account in order to submit a ticket and did so on May 5th and no one has yet to respond. What’s the SLA on support tickets on a paid account?

Thanks.
Kevin.

Hey @kevin2,

Can you share your authorize URL and your request access token url so I can debug?

Thanks,
Tommy

I’m not sure which URL you’re asking for but both of these should work as we have several development environments but only one of them works.

Works: https://zoom.us/oauth/authorize?response_type=code&client_id=jBQQLUuqR_SliP3UAxTxRw&redirect_uri=https://dev3.teamlinkt.com/Webhook/zoomWebhook&state=/events/add/573

This one redirects you to the Zoom login screen as expected.

Does not work: https://zoom.us/oauth/authorize?response_type=code&client_id=jBQQLUuqR_SliP3UAxTxRw&redirect_uri=https://dev6.teamlinkt.com/Webhook/zoomWebhook&state=/events/add/573

This one returns the “Invalid redirect url (4,700)” error.

Hey @kevin2,

Gotcha - looks like this is an issue with the new redirect url not updating on certain clusters. I will have engineering look into this. (ZOOM-162618)

Thanks,
Tommy

Great! Thank you.
Kevin

Hi Tommy.

Any update on this?

Thanks.
Kevin.

Hey @kevin2,

Not yet. I have just escalated this.

Thanks,
Tommy

Hey @kevin2,

It should be fixed now! :slight_smile:

Please try and let me know.

Thanks,
Tommy

Hi @tommy .

I’ve tested again from different url’s and they do appear to be working now. I’m no longer getting the error.

Thanks for fixing the problem!

Kevin.