# S2S OAuth app cannot select phone\_sms:write:admin - SMS send scope missing from Add Scopes picker

**URL:** <https://devforum.zoom.us/t/s2s-oauth-app-cannot-select-phone-smsadmin-sms-send-scope-missing-from-add-scopes-picker/147999>\
**Category:** API and Webhooks\
**Tags:** phone, api\
**Created:** [November 15, 2026, 1:26am UTC](https://devforum.zoom.us/t/s2s-oauth-app-cannot-select-phone-smsadmin-sms-send-scope-missing-from-add-scopes-picker/147999 "2026-11-15T01:26:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Accounting1](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@Accounting1](https://devforum.zoom.us/u/Accounting1)\
**Post date:** [November 15, 2026, 1:26am UTC](https://devforum.zoom.us/t/s2s-oauth-app-cannot-select-phone-smsadmin-sms-send-scope-missing-from-add-scopes-picker/147999/1 "2026-11-15T01:26:14Z")

</div>

[redacted]

We are building an internal staff app that reads and replies to texts on our three Zoom Phone numbers.

**What works:** the SMS read scopes (phone:read:list\_sms\_sessions:admin, phone:read:sms\_session:admin, phone:read:sms\_message:admin) are selectable and GET /phone/sms/sessions returns our threads.

**What does not:** the write scope for POST /phone/sms/messages (phone\_sms:write:admin / phone:write:sms:admin) does not appear anywhere in the Add Scopes picker for this app, so sends fail with “Invalid access token, does not contain scopes”. Searching the picker for “sms” only shows the phone:read:\* scopes and Contact Center scopes.

10DLC brand (GatherGrounds Resorts) and campaign (CFW7JSB) are approved and SMS is active on the numbers. Zoom Support case TS2497368 was closed as “configuration-related, outside the Developer Support Plan” and pointed us here.

Can a developer advocate enable the Zoom Phone SMS write scope for this account/app, or tell us what is required to get it exposed in the picker?

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [November 16, 2026, 2:53pm UTC](https://devforum.zoom.us/t/s2s-oauth-app-cannot-select-phone-smsadmin-sms-send-scope-missing-from-add-scopes-picker/147999/3 "2026-11-16T14:53:16Z")

</div>

Hi @Accounting1 ,

> [@Accounting1](#):
>
> **What works:** the SMS read scopes (phone:read:list\_sms\_sessions:admin, phone:read:sms\_session:admin, phone:read:sms\_message:admin) are selectable and GET /phone/sms/sessions returns our threads.
> 
> **What does not:** the write scope for POST /phone/sms/messages (phone\_sms:write:admin / phone:write:sms:admin) does not appear anywhere in the Add Scopes picker for this app, so sends fail with “Invalid access token, does not contain scopes”. Searching the picker for “sms” only shows the phone:read:\* scopes and Contact Center scopes.
> 
> 10DLC brand (GatherGrounds Resorts) and campaign (CFW7JSB) are approved and SMS is active on the numbers. Zoom Support case TS2497368 was closed as “configuration-related, outside the Developer Support Plan” and pointed us here.

What may be happening here is that the user who is trying to enable these scopes do not have “Write” permissions enabled. Can you double check that the account owner or a Super Admin (admin user who has essentially the same permissions as the account owner) give the developer who is scoping the app “Write” permissions?

> **[Using role management](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0064983)**
>
> Each user in a Zoom account automatically has a system role, which can be owner, administrator, or member.
