# Trouble using in-client OAuth silently (\`authorize\` API)

**URL:** <https://devforum.zoom.us/t/trouble-using-in-client-oauth-silently-authorize-api/77634>\
**Category:** Zoom Apps\
**Created:** [October 19, 2022, 7:37pm UTC](https://devforum.zoom.us/t/trouble-using-in-client-oauth-silently-authorize-api/77634 "2022-10-19T19:37:07Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![om7](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/om7/32/36428_2.png) [@om7](https://devforum.zoom.us/u/om7)\
**Post date:** [November 16, 2022, 7:39pm UTC](https://devforum.zoom.us/t/trouble-using-in-client-oauth-silently-authorize-api/77634/8 "2022-11-16T19:39:47Z")

</div>

The bug was on our end;

When calling POST [https://zoom.us/oauth/token](https://zoom.us/oauth/token) (from [the docs here](https://marketplace.zoom.us/docs/guides/auth/oauth/#step-2-request-access-token))

We were using the wrong `redirect_uri` value in the request body.

We are now using our front-end web application’s URL when doing in-client OAuth, instead of redirecting to our back-end auth URL (as we do when a user installs from the browser).

---

_[View the full topic](https://devforum.zoom.us/t/trouble-using-in-client-oauth-silently-authorize-api/77634)._