# /me endpoint support information **URL:** \ **Category:** API and Webhooks\ **Created:** [June 6, 2019, 9:37pm UTC](https://devforum.zoom.us/t/me-endpoint-support-information/4552 "2019-06-06T21:37:44Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![tpenedo](https://avatars.discourse-cdn.com/v4/letter/t/97f17d/32.png) [@tpenedo](https://devforum.zoom.us/u/tpenedo)\ **Post date:** [June 6, 2019, 9:37pm UTC](https://devforum.zoom.us/t/me-endpoint-support-information/4552/1 "2019-06-06T21:37:44Z")
Hi there, I am currently migrating our integration with zoom from V1 to V2, and am implementing the OAuth 2 authentication. I am curious on a couple things: - Given that a user grants authorization to the application and access and refresh tokens are successfully generated, am i able to create meetings on their behalf without their userId? Using /me endpoints? Which endpoints are supported? I haven’t found much information about it. Or are userId’s always required in the url? - If the userId is required, what is the easiest way to obtain those for an organization given i am an admin? ---
**Author:** ![ojus.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ojus.zoom/32/734_2.png) [@ojus.zoom](https://devforum.zoom.us/u/ojus.zoom)\ **Post date:** [June 6, 2019, 11:03pm UTC](https://devforum.zoom.us/t/me-endpoint-support-information/4552/2 "2019-06-06T23:03:44Z")
Hi @tpenedo, Welcome to the Zoom Developer Community! You would still need the userID to create meetings on their behalf. You can find a list of /me endpoints that are supported here: [https://marketplace.zoom.us/docs/guides/app-submission-and-management/reference](https://marketplace.zoom.us/docs/guides/app-submission-and-management/reference) To get the userID, you can consider calling this API: > **[List Users - Users - Zoom API - API Reference](https://marketplace.zoom.us/docs/api-reference/zoom-api/users/users)** > > List users on your account. > Scopes: user:read:admin > > Authorization > > Request Parameters > > Responses > > Send a Test Request Please let me know if you have any questions. Thanks! ---
**Author:** ![tpenedo](https://avatars.discourse-cdn.com/v4/letter/t/97f17d/32.png) [@tpenedo](https://devforum.zoom.us/u/tpenedo)\ **Post date:** [June 10, 2019, 1:32pm UTC](https://devforum.zoom.us/t/me-endpoint-support-information/4552/3 "2019-06-10T13:32:20Z")
Hi Ojus, The reference page you’ve provided for the /me context explicitly says " you can use `me` in place of the **User ID** to restrict the context of the call to the user that token belongs to". Wouldn’t this mean i don’t need the userId to create meetings on their behalf, since the access token i am passing would restrict the context of the call to that user? ---
**Author:** ![ojus.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ojus.zoom/32/734_2.png) [@ojus.zoom](https://devforum.zoom.us/u/ojus.zoom)\ **Post date:** [June 13, 2019, 10:40pm UTC](https://devforum.zoom.us/t/me-endpoint-support-information/4552/4 "2019-06-13T22:40:13Z")
@tpenedo, we have recently updated our docs. > [@tpenedo](#): > > The reference page you’ve provided for the /me context explicitly says " you can use `me` in place of the **User ID** to restrict the context of the call to the user that token belongs to" Allow me to work with my engineering team and get back to you with an update on this. ---
**Author:** ![tpenedo](https://avatars.discourse-cdn.com/v4/letter/t/97f17d/32.png) [@tpenedo](https://devforum.zoom.us/u/tpenedo)\ **Post date:** [June 27, 2019, 2:27pm UTC](https://devforum.zoom.us/t/me-endpoint-support-information/4552/5 "2019-06-27T14:27:28Z")
HI Ojus, Any confirmation on this? ---
**Author:** ![ojus.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ojus.zoom/32/734_2.png) [@ojus.zoom](https://devforum.zoom.us/u/ojus.zoom)\ **Post date:** [June 28, 2019, 11:48pm UTC](https://devforum.zoom.us/t/me-endpoint-support-information/4552/6 "2019-06-28T23:48:53Z")
@tpenedo, Apologies for the delay, I will update you by early next week. Thanks ---
**Author:** ![tpenedo](https://avatars.discourse-cdn.com/v4/letter/t/97f17d/32.png) [@tpenedo](https://devforum.zoom.us/u/tpenedo)\ **Post date:** [July 17, 2019, 2:53pm UTC](https://devforum.zoom.us/t/me-endpoint-support-information/4552/7 "2019-07-17T14:53:37Z")
Hi Ojus, Any confirmation? ---
**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\ **Post date:** [July 17, 2019, 8:08pm UTC](https://devforum.zoom.us/t/me-endpoint-support-information/4552/9 "2019-07-17T20:08:16Z")
Hey @tpenedo, If you have the user’s access token, you can easily [JWT parse](https://jwt.io/) it to get the userId, and then make calls to the [create a meeting endpoint](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate) to create meetings on behalf of a user. Here is an example of a JWT parsed access\_token. ![54%20PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/2X/9/954f365c6c87cf2b5fcf80998ec90f5c6a7ee48c.png) [Try pasting an access\_token in the debugger section here to see an example.](https://jwt.io/) Let me know if this helps! ---
**Author:** ![tpenedo](https://avatars.discourse-cdn.com/v4/letter/t/97f17d/32.png) [@tpenedo](https://devforum.zoom.us/u/tpenedo)\ **Post date:** [July 17, 2019, 9:26pm UTC](https://devforum.zoom.us/t/me-endpoint-support-information/4552/10 "2019-07-17T21:26:55Z")
> [@tommy](#): > > if th thanks Tommy, I’m building this application in Apex/Salesforce and don’t have an easy way to JWT-parse the access token. I simply just want to confirm this section in your documentation is actually supported: [https://marketplace.zoom.us/docs/guides/authorization/oauth/oauth-with-zoom](https://marketplace.zoom.us/docs/guides/authorization/oauth/oauth-with-zoom) ![18%20PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/2X/a/a096aadbb8cdea76bdee7751118e429775a62cee.png) ---
**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\ **Post date:** [July 17, 2019, 9:41pm UTC](https://devforum.zoom.us/t/me-endpoint-support-information/4552/11 "2019-07-17T21:41:05Z")
@tpenedo, I see. Yes this is supported. You can use `/me` instead of the `{{User ID}}` which will derive the user from the `access_token` in the authorization bearer header. Thanks, Tommy ---
**Author:** ![tpenedo](https://avatars.discourse-cdn.com/v4/letter/t/97f17d/32.png) [@tpenedo](https://devforum.zoom.us/u/tpenedo)\ **Post date:** [July 18, 2019, 1:04pm UTC](https://devforum.zoom.us/t/me-endpoint-support-information/4552/12 "2019-07-18T13:04:47Z")
Thanks, Tommy, my question is answered. I asked because initially i didn’t see much documentation on it and wanted to confirm. Thanks again. ---
**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\ **Post date:** [July 18, 2019, 3:14pm UTC](https://devforum.zoom.us/t/me-endpoint-support-information/4552/13 "2019-07-18T15:14:34Z")
Happy to help @tpenedo! We will add to the documentation to make this feature more clear.