# Server to Server Authentication Missing Scopes

**URL:** <https://devforum.zoom.us/t/server-to-server-authentication-missing-scopes/137831>\
**Category:** API and Webhooks\
**Created:** [October 3, 2025, 3:12pm UTC](https://devforum.zoom.us/t/server-to-server-authentication-missing-scopes/137831 "2025-10-03T15:12:04Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Smwest87](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/smwest87/32/71569_2.png) [@Smwest87](https://devforum.zoom.us/u/Smwest87)\
**Post date:** [October 3, 2025, 3:12pm UTC](https://devforum.zoom.us/t/server-to-server-authentication-missing-scopes/137831/1 "2025-10-03T15:12:04Z")

</div>

**Scopes Missing for Server to Server Authentication  
Description**  
_When creating a new server to server authentication the scopes meeting:write:meeting:admin are not available to be selected. This is a result of permissions for sure, however our security team is cautious to give developers admin permissions similar to some other posts (which your site will not let me link_ ☹ ).

What are the minimum necessary permissions for the application to create a meeting?

Security is concerned providing these permissions:  
Account Management: Account Profile

Account Management: Account Settings

User and Perm Management: Users

---

<div class="post-metadata">

**Author:** ![Henry6](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/henry6/32/51499_2.png) [@Henry6](https://devforum.zoom.us/u/Henry6)\
**Post date:** [October 6, 2025, 6:40am UTC](https://devforum.zoom.us/t/server-to-server-authentication-missing-scopes/137831/2 "2025-10-06T06:40:45Z")

</div>

“Missing scopes in server-to-server authentication usually mean the required permissions weren’t set correctly during configuration. Double-check the scope values in your API settings and ensure they align with what the application is requesting. I also share useful guides and creative resources on my app”

---

<div class="post-metadata">

**Author:** ![Smwest87](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/smwest87/32/71569_2.png) [@Smwest87](https://devforum.zoom.us/u/Smwest87)\
**Post date:** [October 6, 2025, 6:07pm UTC](https://devforum.zoom.us/t/server-to-server-authentication-missing-scopes/137831/3 "2025-10-06T18:07:09Z")

</div>

Correct. We are wanting to identify the exact required permissions for meeting:write to display in the Scopes option

---

<div class="post-metadata">

**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 8, 2025, 5:53pm UTC](https://devforum.zoom.us/t/server-to-server-authentication-missing-scopes/137831/4 "2025-10-08T17:53:49Z")

</div>

Hi @Smwest87  
Thanks for reaching out to us!  
To be able to add the _meeting:write:meeting:admin_ scope in a Server to Server OAuth app, your developer role should have at least the Users permission settings enable to view and edit

 ![Screenshot 2025-10-08 at 1.52.42 PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/5/6521ed34aedbc7bcdd0524c20c3c72db05fcefc5.png)

---

<div class="post-metadata">

**Author:** ![Ryan15](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ryan15/32/71670_2.png) [@Ryan15](https://devforum.zoom.us/u/Ryan15)\
**Post date:** [October 8, 2025, 6:47pm UTC](https://devforum.zoom.us/t/server-to-server-authentication-missing-scopes/137831/5 "2025-10-08T18:47:26Z")

</div>

Hi @elisa.zoom!  
So for an application to be able to create a meeting, the user account needs to be able to edit user information? All we’re trying to do is have an integration create a meeting so I’m not sure why admin scopes are required for that.

---

<div class="post-metadata">

**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 8, 2025, 6:50pm UTC](https://devforum.zoom.us/t/server-to-server-authentication-missing-scopes/137831/6 "2025-10-08T18:50:26Z")

</div>

Yes @Ryan15  
This is because a Server to Server Oauth app is an account Admin level app.  
You could work with a General Oauth app to have more granularity

---

<div class="post-metadata">

**Author:** ![Smwest87](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/smwest87/32/71569_2.png) [@Smwest87](https://devforum.zoom.us/u/Smwest87)\
**Post date:** [October 8, 2025, 8:19pm UTC](https://devforum.zoom.us/t/server-to-server-authentication-missing-scopes/137831/7 "2025-10-08T20:19:12Z")

</div>

Hey Elisa,

The simplicity of Server to Server authentication is the main reason we leaned towards it. Having to create an OAuth flow to handle our use case seemed like a large lift compared to calling for an access token and using it. General apps can only use the OAuth flow is that correct?

---

<div class="post-metadata">

**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 9, 2025, 4:47pm UTC](https://devforum.zoom.us/t/server-to-server-authentication-missing-scopes/137831/8 "2025-10-09T16:47:10Z")

</div>

You are correct, General apps can only use the OAuth flow.

---

<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:** [November 12, 2025, 3:13pm UTC](https://devforum.zoom.us/t/server-to-server-authentication-missing-scopes/137831/9 "2025-11-12T15:13:53Z")

</div>

Closed on November 12, 2025, 3:13pm UTC

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