# Zoom Jsonrpc API: This API does not support oAuth2 for authorization **URL:** \ **Category:** API and Webhooks\ **Tags:** oauth, meeting-sdk, zoom-room\ **Created:** [October 13, 2022, 12:48pm UTC](https://devforum.zoom.us/t/zoom-jsonrpc-api-this-api-does-not-support-oauth2-for-authorization/77354 "2022-10-13T12:48:10Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![maksym.rossiitsev](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@maksym.rossiitsev](https://devforum.zoom.us/u/maksym.rossiitsev)\ **Post date:** [October 13, 2022, 12:48pm UTC](https://devforum.zoom.us/t/zoom-jsonrpc-api-this-api-does-not-support-oauth2-for-authorization/77354/1 "2022-10-13T12:48:10Z")
Hi, I’m trying to move functionality, previously based on JWT authentication to OAuth, and it seems like everything works fine now, but I have noticed that whenever I issue “join a meeting” request ([Zoom Rooms API](https://marketplace.zoom.us/docs/guides/zoom-rooms/zoom-rooms-api/)) I receive this error(works fine with JWT → [https://api.zoom.us:443/v2/rooms/{id}/meetings](https://api.zoom.us:443/v2/rooms/%7Bid%7D/meetings)): 401 : [{“code”:124,“message”:“This API does not support oAuth2 for authorization.”}] I’ve tried to edit the OAuth Server-to-server app scopes, but maybe it’s more complicated than that, or the functionality isn’t going to be supported for OAuth, so I wanted to check if there’s something I should do about it, or if the migration isn’t fully complete yet or something… Thank you! ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [October 13, 2022, 1:17pm UTC](https://devforum.zoom.us/t/zoom-jsonrpc-api-this-api-does-not-support-oauth2-for-authorization/77354/2 "2022-10-13T13:17:46Z")
Hi @maksym.rossiitsev Thanks for reaching out to the Zoom Developer Forum, I am happy to help here! There are new APIs that support the Server to Server OAuth for Zoom Rooms > **[Zoom Meeting API](https://marketplace.zoom.us/docs/api-reference/zoom-api/methods/#tag/Zoom-Rooms)** > > API Reference for /api-reference/zoom-api/methods Could you please take a look into this and let me know if this helps? Best Elisa ---
**Author:** ![maksym.rossiitsev](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@maksym.rossiitsev](https://devforum.zoom.us/u/maksym.rossiitsev)\ **Post date:** [October 13, 2022, 1:43pm UTC](https://devforum.zoom.us/t/zoom-jsonrpc-api-this-api-does-not-support-oauth2-for-authorization/77354/3 "2022-10-13T13:43:42Z")
Ok, I see, thank you! I will take a look at it now, just one small question first - does this mean that the “old” API is going to be deprecated soon also? Or is it only RPC that won’t work with OAuth? ---
**Author:** ![maksym.rossiitsev](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@maksym.rossiitsev](https://devforum.zoom.us/u/maksym.rossiitsev)\ **Post date:** [October 13, 2022, 5:15pm UTC](https://devforum.zoom.us/t/zoom-jsonrpc-api-this-api-does-not-support-oauth2-for-authorization/77354/4 "2022-10-13T17:15:11Z")
Ok I have checked the APIs you have shared and yes - this is the one we’ve been using thus far. However, we are also using RPC endpoints for ZR controls (join meeting using PMI, end meeting, restart ZR client etc) and it doesn’t seem that these endpoints work with OAuth… So my question is - is it official that there’s no OAuth support for such functionality, or is it something that we can expect to work in future? Thank you! ---
**Author:** ![albert.ananos](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/albert.ananos/32/46518_2.png) [@albert.ananos](https://devforum.zoom.us/u/albert.ananos)\ **Post date:** [March 16, 2023, 7:56pm UTC](https://devforum.zoom.us/t/zoom-jsonrpc-api-this-api-does-not-support-oauth2-for-authorization/77354/5 "2023-03-16T19:56:25Z")
Hi, I think we have the same problem. We are migrating python programs that invite some rooms when a meeting starts in a master room using url = ‘[https://api.zoom.us/v2/rooms/](https://api.zoom.us/v2/rooms/)’ + MainRoomID + ‘/meetings’ params = {‘jsonrpc’: ‘2.0’, ‘method’: ‘invite’, ‘params’: {“callee”: AuxRoomID}} It works perfectly with JWT, but OAuth causes an error: “This API does not support oAuth2 for authorization.” Should we use another API for this functionality? Thanks. ---
**Author:** ![MultiplayerSession](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/multiplayersession/32/66446_2.png) [@MultiplayerSession](https://devforum.zoom.us/u/MultiplayerSession)\ **Post date:** [March 16, 2023, 9:14pm UTC](https://devforum.zoom.us/t/zoom-jsonrpc-api-this-api-does-not-support-oauth2-for-authorization/77354/6 "2023-03-16T21:14:31Z")
Looks like the equivalent operations are now part of [Use Zoom Room controls (`PATCH /rooms/{id}/events`)](https://marketplace.zoom.us/docs/api-reference/zoom-api/methods/#operation/ZoomRoomsControls) with different values for `method`. I don’t see a documented equivalent for the `callback_url` parameter, so you might need to experiment to find an alternative. ---
**Author:** ![albert.ananos](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/albert.ananos/32/46518_2.png) [@albert.ananos](https://devforum.zoom.us/u/albert.ananos)\ **Post date:** [March 17, 2023, 7:27pm UTC](https://devforum.zoom.us/t/zoom-jsonrpc-api-this-api-does-not-support-oauth2-for-authorization/77354/7 "2023-03-17T19:27:16Z")
Thank you, Christopher. That did the trick! 🙂 ---
**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:** [January 10, 2025, 8:41pm UTC](https://devforum.zoom.us/t/zoom-jsonrpc-api-this-api-does-not-support-oauth2-for-authorization/77354/9 "2025-01-10T20:41:10Z")
This topic was automatically closed 368 days after the last reply. New replies are no longer allowed.