# POST https://api.zoom.us/v2/users/me/meetings) 403 {"code":403,"message":"Authenticated user has not permitted access to the targeted resource."}

**URL:** <https://devforum.zoom.us/t/post-https-api-zoom-us-v2-users-me-meetings-403-code-403-message-authenticated-user-has-not-permitted-access-to-the-targeted-resource/72233>\
**Category:** Meetings\
**Created:** [July 14, 2022, 1:39pm UTC](https://devforum.zoom.us/t/post-https-api-zoom-us-v2-users-me-meetings-403-code-403-message-authenticated-user-has-not-permitted-access-to-the-targeted-resource/72233 "2022-07-14T13:39:05Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![prashanth1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/prashanth1/32/39397_2.png) [@prashanth1](https://devforum.zoom.us/u/prashanth1)\
**Post date:** [July 14, 2022, 1:39pm UTC](https://devforum.zoom.us/t/post-https-api-zoom-us-v2-users-me-meetings-403-code-403-message-authenticated-user-has-not-permitted-access-to-the-targeted-resource/72233/1 "2022-07-14T13:39:05Z")

</div>

Hi,  
I am facing an issue when trying to create meeting with Zoom API  
POST [https://api.zoom.us/v2/users/me/meetings](https://api.zoom.us/v2/users/me/meetings)) 403 {“code”:403,“message”:“Authenticated user has not permitted access to the targeted resource.”}

I already have permission for “meetings:write”.

**But, the same API works if user has allowed “Shared access permissions”**

**Question is: Why do we need shared access permission to create meetings for a single user who is owner of the account?**

---

<div class="post-metadata">

**Author:** ![bryandantas1](https://avatars.discourse-cdn.com/v4/letter/b/53a042/32.png) [@bryandantas1](https://devforum.zoom.us/u/bryandantas1)\
**Post date:** [August 5, 2022, 2:04am UTC](https://devforum.zoom.us/t/post-https-api-zoom-us-v2-users-me-meetings-403-code-403-message-authenticated-user-has-not-permitted-access-to-the-targeted-resource/72233/2 "2022-08-05T02:04:48Z")

</div>

Same problem here, have you found a solution to create meeting without marking shared permission?

---

<div class="post-metadata">

**Author:** ![prashanth1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/prashanth1/32/39397_2.png) [@prashanth1](https://devforum.zoom.us/u/prashanth1)\
**Post date:** [August 5, 2022, 4:58pm UTC](https://devforum.zoom.us/t/post-https-api-zoom-us-v2-users-me-meetings-403-code-403-message-authenticated-user-has-not-permitted-access-to-the-targeted-resource/72233/3 "2022-08-05T16:58:22Z")

</div>

not yet… unfortunately

---

<div class="post-metadata">

**Author:** ![prashanth1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/prashanth1/32/39397_2.png) [@prashanth1](https://devforum.zoom.us/u/prashanth1)\
**Post date:** [August 11, 2022, 11:11am UTC](https://devforum.zoom.us/t/post-https-api-zoom-us-v2-users-me-meetings-403-code-403-message-authenticated-user-has-not-permitted-access-to-the-targeted-resource/72233/4 "2022-08-11T11:11:08Z")

</div>

can someone in the community help… i tried many things but still couldnt figure out a way to create without shared permission enabled. This is a user level app and I have meetings read:write permission.

Still i get “no permitted access to the targeted resource”

---

<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:** [August 12, 2022, 1:37am UTC](https://devforum.zoom.us/t/post-https-api-zoom-us-v2-users-me-meetings-403-code-403-message-authenticated-user-has-not-permitted-access-to-the-targeted-resource/72233/5 "2022-08-12T01:37:45Z")

</div>

Hi @prashanth1  
I am really sorry we did not reply to your post earlier! I am happy to help troubleshoot this issue.  
Could you please confirm if your app is published in the Marketplace? If so, could you please share the name of the application with me and take a look into this.  
Best,  
Elisa

---

<div class="post-metadata">

**Author:** ![prashanth1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/prashanth1/32/39397_2.png) [@prashanth1](https://devforum.zoom.us/u/prashanth1)\
**Post date:** [August 23, 2022, 11:47am UTC](https://devforum.zoom.us/t/post-https-api-zoom-us-v2-users-me-meetings-403-code-403-message-authenticated-user-has-not-permitted-access-to-the-targeted-resource/72233/6 "2022-08-23T11:47:09Z")

</div>

Hi @elisa.zoom ,  
Thank you for responding. Sorry for getting back late. We are really stuck with this issue and not able to roll out our zoom integration.

Our app “Leadmonk” is in functional review currently and its stuck in that.

We did a straight forward zoom integration using oauth. But for creating a meeting, I keep getting the error  
POST [https://api.zoom.us/v2/users/me/meetings](https://api.zoom.us/v2/users/me/meetings)) 403 {“code”:403,“message”:“Authenticated user has not permitted access to the targeted resource.”}

but GET [https://api.zoom.us/v2/users/me](https://api.zoom.us/v2/users/me) works fine.

App has “meetings:write” permission.

The same call (POST [https://api.zoom.us/v2/users/me/meetings](https://api.zoom.us/v2/users/me/meetings)) works, if user provides “Shared access permission”. This is strange, as we are just making call to the account where user is the owner.

Any help to create meetings without “shared access permission” would be great.

Thank you

---

<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:** [August 23, 2022, 3:47pm UTC](https://devforum.zoom.us/t/post-https-api-zoom-us-v2-users-me-meetings-403-code-403-message-authenticated-user-has-not-permitted-access-to-the-targeted-resource/72233/7 "2022-08-23T15:47:00Z")

</div>

Hi @prashanth1  
Do not worry about it…  
This is an interesting case cause I have not seen this issue with other apps.  
I tried creating a user-level app on my end and called both endpoints and it works just fine with Shared access permission and without it.

Have you heard anything back from the Functional review team?  
Best,  
Elisa

---

<div class="post-metadata">

**Author:** ![prashanth1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/prashanth1/32/39397_2.png) [@prashanth1](https://devforum.zoom.us/u/prashanth1)\
**Post date:** [August 23, 2022, 5:37pm UTC](https://devforum.zoom.us/t/post-https-api-zoom-us-v2-users-me-meetings-403-code-403-message-authenticated-user-has-not-permitted-access-to-the-targeted-resource/72233/8 "2022-08-23T17:37:08Z")

</div>

Hi @elisa.zoom  
Yes, most of the others apps I tested, don’t need “shared access”.

I submitted again for functional review, but I am assuming they will reject. I am unable to get it working without “shared access permission”.

Looks like few others are facing similar issue. for example. @bryandantas1 who replied in this thread.

Also,

> [@Getting error Authenticated user has not permitted access to the targeted resource while creating meeting](https://devforum.zoom.us/t/getting-error-authenticated-user-has-not-permitted-access-to-the-targeted-resource-while-creating-meeting/74413):
>
> Hi There, We are receiving an error while creating meeting, Authenticated user has not permitted access to the targeted resource. however we get this error only when user authenticate zoom account whithout checking Allow this app to use my shared access permissions and if user checks this checkbox we dont get any error while creating metting and meeting getting created normally. we are usig following scopes in our app

So, not sure how where the issue is or how to proceed.

any guidance will help.

Thank you,

---

<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:** [August 23, 2022, 8:35pm UTC](https://devforum.zoom.us/t/post-https-api-zoom-us-v2-users-me-meetings-403-code-403-message-authenticated-user-has-not-permitted-access-to-the-targeted-resource/72233/9 "2022-08-23T20:35:31Z")

</div>

Thanks for sharing more details with me @prashanth1  
I will go ahead and reach out to the Marketplace about this issue.

---

<div class="post-metadata">

**Author:** ![prashanth1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/prashanth1/32/39397_2.png) [@prashanth1](https://devforum.zoom.us/u/prashanth1)\
**Post date:** [August 25, 2022, 5:13am UTC](https://devforum.zoom.us/t/post-https-api-zoom-us-v2-users-me-meetings-403-code-403-message-authenticated-user-has-not-permitted-access-to-the-targeted-resource/72233/10 "2022-08-25T05:13:30Z")

</div>

@elisa.zoom the solution posted here by @jovy did the trick.

> [@Getting error Authenticated user has not permitted access to the targeted resource while creating meeting](https://devforum.zoom.us/t/getting-error-authenticated-user-has-not-permitted-access-to-the-targeted-resource-while-creating-meeting/74413/6):
>
> Hi @prashanth1 We had a call with zoom testing team and discussed this issue with them, issue was we need to remove schedule\_for parameter while creating meeting because as their developer said this schedule\_for needs shared access permission. so after removing request to create meeting become like this. settings = { 'enable': True, 'host\_video': True, 'cn\_meeting': True, 'in\_meeting': True, 'join\_before\_host': True, 'mute\_upon\_entry': False, …

---

<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:** [August 25, 2022, 5:29pm UTC](https://devforum.zoom.us/t/post-https-api-zoom-us-v2-users-me-meetings-403-code-403-message-authenticated-user-has-not-permitted-access-to-the-targeted-resource/72233/11 "2022-08-25T17:29:50Z")

</div>

Hey @prashanth1  
Thanks for sharing this with me.  
I did not know about this issue, so I appreciate you sharing this with me and the community!  
Cheers,  
Elisa
