# Exact scope for GET /v2/users/me on an Admin-managed General App

**URL:** <https://devforum.zoom.us/t/exact-scope-for-get-v2-users-me-on-an-admin-managed-general-app/146257>\
**Category:** Meetings\
**Created:** [September 6, 2026, 6:43pm UTC](https://devforum.zoom.us/t/exact-scope-for-get-v2-users-me-on-an-admin-managed-general-app/146257 "2026-09-06T18:43:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Coactivy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/coactivy/32/76492_2.png) [@Coactivy](https://devforum.zoom.us/u/Coactivy)\
**Post date:** [September 6, 2026, 6:43pm UTC](https://devforum.zoom.us/t/exact-scope-for-get-v2-users-me-on-an-admin-managed-general-app/146257/1 "2026-09-06T18:43:27Z")

</div>

Hi Zoom team,

We have a current **General App configured as Admin-managed**.

Immediately after OAuth token exchange, our backend needs to call:

`GET https://api.zoom.us/v2/users/me`

Could you please confirm:

1. What is the **exact current OAuth scope name** that must be selected in the Marketplace builder and requested for this endpoint on an Admin-managed General App?
2. Under an Admin-managed authorization grant, what does the literal `me` resolve to — the admin who authorized the app, the account owner, or another principal?

We have seen references to `user:read`, `user:read:admin`, as well as newer granular scope variants, so we want to avoid relying on legacy scope naming.

We only need the current **General App / Admin-managed** behavior for `GET /v2/users/me`.

Thanks.

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [September 8, 2026, 5:34am UTC](https://devforum.zoom.us/t/exact-scope-for-get-v2-users-me-on-an-admin-managed-general-app/146257/2 "2026-09-08T05:34:18Z")

</div>

@Coactivy [Zoom User API - API - Zoom Developer Docs](https://developers.zoom.us/docs/api/rest/reference/user/methods/#operation/user).

“me” should work properly for user-managed app.

Have you tried using a user-managed app?
