# In-client OAuth (\`authorize\` API) is not silent **URL:** \ **Category:** Zoom Apps\ **Created:** [January 21, 2025, 4:40pm UTC](https://devforum.zoom.us/t/in-client-oauth-authorize-api-is-not-silent/125029 "2025-01-21T16:40:21Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![tkishkin](https://avatars.discourse-cdn.com/v4/letter/t/57b2e6/32.png) [@tkishkin](https://devforum.zoom.us/u/tkishkin)\ **Post date:** [February 12, 2025, 11:51am UTC](https://devforum.zoom.us/t/in-client-oauth-authorize-api-is-not-silent/125029/8 "2025-02-12T11:51:50Z")
Hi @donte.zoom , as I already mentioned in the community forum, a fix was found thanks to your suggestion. All I had to do was to add under _“OAuth Allow Lists”_ the URL of the page from which the `zoomSdk.authorize` call was being made. In my case, `https://zoom-cross-tenant.staging-linkando.com/zoomapp`. Indeed, the [documentation](https://developers.zoom.us/docs/zoom-apps/authentication/#enabling-in-client-oauth-for-your-app) mentiones: "_under the OAuth allow list section, add your app’s Home URL"_. The confusion in my case was due to the fact that my home URL redirects the user further to another subdomain, and only after that the `zoomSdk.authorize` is called. Maybe it’s worth rewording the documentation slightly to avoid such confusions. Another adjustment I had to do was to send the current page URL (again, `.../zoomapp`) as `redirect_uri` when requesting `https://zoom.us/oauth/token` from the server. Initially I used to send my main _OAuth Redirect URL_ like in in-browser auth, which led to `invalid_grant` error. Similar to [this issue in another user’s forum post](https://devforum.zoom.us/t/trouble-using-in-client-oauth-silently-authorize-api/77634/8). Thanks for the support @donte.zoom ! --- _[View the full topic](https://devforum.zoom.us/t/in-client-oauth-authorize-api-is-not-silent/125029)._