# OBF token with admin granted scopes

**URL:** <https://devforum.zoom.us/t/obf-token-with-admin-granted-scopes/140381>\
**Category:** Meeting SDK\
**Tags:** api, sdk\
**Created:** [January 11, 2026, 7:49am UTC](https://devforum.zoom.us/t/obf-token-with-admin-granted-scopes/140381 "2026-01-11T07:49:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Suresh4](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/suresh4/32/49580_2.png) [@Suresh4](https://devforum.zoom.us/u/Suresh4)\
**Post date:** [January 11, 2026, 7:49am UTC](https://devforum.zoom.us/t/obf-token-with-admin-granted-scopes/140381/1 "2026-01-11T07:49:47Z")

</div>

Hi Team,

I have a question about using OBF tokens for [Meeting SDK](https://developers.zoom.us/docs/meeting-sdk) apps.

I’ve reviewed the following documents:

- OBF token transition blog:  
/blog/transition-to-obf-token-meetingsdk-apps/

- “Get a user’s token” API:  
/docs/api/rest/reference/user/methods/#operation/userToken

From these, my understanding is that a typical pattern is:

- Each end user authorizes with the granular scope `user:read:token`, and

- The app then calls `GET /users/me/token?type=onbehalf` to obtain an OBF token.

I’d like to confirm a point:

1. **Using admin granular scopes**

Any clarification or best-practice guidance for this scenario would be greatly appreciated.

Thanks in advance.