When I attempt to add a new server-to-server Oauth application (using the blue ‘Add’ button under the ‘Add your app’ heading on the ‘Activcation’ step) It will take me to https://zoom.us/oauth/authorize?response_type=code&client_id={ClientId}&redirect_uri=http%3A%2F%2Flocalhost%3A5000%2Fcallback Which then redirects back to http://localhost:5000/callback?code={code}.
I do not define localhost anywhere in my configuration, that seems to be hardcoded somewhere in the zoom website.
The resulting issue is that the app is not being added.
For our OAuth application, the Activation section’s Add button seems to be using the URL we entered in the App Credentials section’s Redirect URL for OAuth field. What field value do you see there?
Thanks, I had not entered a value in that field so I guess it was using a default? However after updating the Redirect URL the application is still not added, is there something I need to do with the code value in the callback? I can’t see it mentioned in the documentation anywhere.
I guess I’m a little confused about which type of app you’re creating. OAuth apps have that Add button, but normally your user-facing workflow would be doing the redirect to Zoom and you’d populate your own URL, so I’m not sure why you’d want to use that Add button. Server-to-Server OAuth apps just have an Activate button. Compare the two types of OAuth apps and see which one makes most sense for your workflow.