# Using Oauth vs WebSDK

**URL:** <https://devforum.zoom.us/t/using-oauth-vs-websdk/72727>\
**Category:** Web\
**Created:** [July 22, 2022, 7:39pm UTC](https://devforum.zoom.us/t/using-oauth-vs-websdk/72727 "2022-07-22T19:39:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dwma1993](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dwma1993/32/37758_2.png) [@dwma1993](https://devforum.zoom.us/u/dwma1993)\
**Post date:** [July 22, 2022, 7:39pm UTC](https://devforum.zoom.us/t/using-oauth-vs-websdk/72727/1 "2022-07-22T19:39:11Z")

</div>

I currently have two different Apps: one OAuth app and one WebSDK app.

The functionality for the OAuth app is a simple app that views and create meetings. The WebSDK only has the functionality of joining/starting existing meetings.

I have a couple of questions:  
1.) Since the WebSDK has its own set of OAuth credentials for starting meetings, is there any reason for me to separate the two apps? Could I just add the functionalities of the OAuth app to the WebSDK app?  
2.) If I wanted to publish the apps, would I have to send approvals for both sets of apps? Would there be any issues with having two separate apps from the same organization?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [August 22, 2022, 5:39am UTC](https://devforum.zoom.us/t/using-oauth-vs-websdk/72727/2 "2022-08-22T05:39:58Z")

</div>

Closed on August 22, 2022, 5:39am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.