# Meeting API permssions

**URL:** <https://devforum.zoom.us/t/meeting-api-permssions/87330>\
**Category:** Meetings\
**Created:** [April 25, 2023, 12:41pm UTC](https://devforum.zoom.us/t/meeting-api-permssions/87330 "2023-04-25T12:41:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![thomas.coon1](https://avatars.discourse-cdn.com/v4/letter/t/e9a140/32.png) [@thomas.coon1](https://devforum.zoom.us/u/thomas.coon1)\
**Post date:** [April 25, 2023, 12:41pm UTC](https://devforum.zoom.us/t/meeting-api-permssions/87330/1 "2023-04-25T12:41:26Z")

</div>

Does use of the Meeting API require any special permission settings or additional account setting? I’ve setup Server to Server OAuth under a Business account and have no problem getting a Bearer Token and using it to list users and get meeting information, but it always returns Bad Request when I try creating a meeting. I used JSON validators to validate the data

curl --location ‘[https://api.zoom.us/v2/users/me/meetings](https://api.zoom.us/v2/users/me/meetings)’   
–header ‘Accept: application/json’   
–header ‘Content-Type: application/json’   
–header ‘Authorization: Bearer eyJzdiI6IjAwMDg’   
–data ‘{  
“topic”: “Testing 01”,  
“type”: 2,  
“start\_time”: “2023-04-27T05:02:00Z”,  
“duration”: “60”,  
“timezone”: “America/Chicago”,  
“password”: “123”,  
“agenda”: “Testing Testing”,  
“settings”: {  
“host\_video”: “true”,  
“participant\_video”: “true”,  
“join\_before\_host”: “true”  
}  
}’

---

<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:** [April 28, 2023, 11:38pm UTC](https://devforum.zoom.us/t/meeting-api-permssions/87330/2 "2023-04-28T23:38:03Z")

</div>

Hi @thomas.coon1 ,

You should be able to create meetings for yourself for sure. Can you please try making the request with the template in our Postman workspace? [Postman](https://www.postman.com/zoom-developer/workspace/zoom-public-workspace/request/22097587-9cab327f-7634-44af-9ee0-1b49f6a6572f)

Thanks!

---

<div class="post-metadata">

**Author:** ![thomas.coon1](https://avatars.discourse-cdn.com/v4/letter/t/e9a140/32.png) [@thomas.coon1](https://devforum.zoom.us/u/thomas.coon1)\
**Post date:** [April 29, 2023, 12:04am UTC](https://devforum.zoom.us/t/meeting-api-permssions/87330/4 "2023-04-29T00:04:42Z")

</div>

I forked off your postman changed userid and Bearer Token (left body untouched) and this is the response:

{  
“code”: 300,  
“message”: “Request Body should be a valid JSON object.”  
}

---

<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:** [May 9, 2023, 12:20am UTC](https://devforum.zoom.us/t/meeting-api-permssions/87330/5 "2023-05-09T00:20:19Z")

</div>

Hi @thomas.coon1 ,

This could be due to some of the fields and values in the Body example. I should have prompted you to remove those things, but I’ve just edited the example to match our documentation. It should work and feel free to customize the request body to what suits your needs 🙂