# Not a "valid JSON object"

**URL:** <https://devforum.zoom.us/t/not-a-valid-json-object/28451>\
**Category:** API and Webhooks\
**Created:** [August 28, 2020, 2:14pm UTC](https://devforum.zoom.us/t/not-a-valid-json-object/28451 "2020-08-28T14:14:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![coda](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/coda/32/6871_2.png) [@coda](https://devforum.zoom.us/u/coda)\
**Post date:** [August 28, 2020, 2:14pm UTC](https://devforum.zoom.us/t/not-a-valid-json-object/28451/1 "2020-08-28T14:14:49Z")

</div>

I am testing with creating a new Meeting via the API.

I am getting this error:  
`{"code":300,"message":"Request Body should be a valid JSON object."}`

With this JSON, which seems valid and passes validation:

```
{
	"topic": "Test 28/8",
	"type": "1",
	"start_time": "2020-08-28T16:30:00",
	"timezone": "Asia/Jerusalem",
	"duration": "60",
	"password": "112233",
	"settings": {
		"host_video": "true",
		"participant_video": "true",
		"cn_meeting": "false",
		"in_meeting": "false",
		"join_before_host": "true",
		"mute_upon_entry": "true",
		"watermark": "true",
		"use_pmi": "boolean",
		"approval_type": "0",
		"registration_type": "0",
		"audio": "both",
		"auto_recording": "none",
		"registrants_email_notification": "false"
	}
}

```

Can someone shed some light on this?  
Thanks!

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 28, 2020, 2:15pm UTC](https://devforum.zoom.us/t/not-a-valid-json-object/28451/2 "2020-08-28T14:15:06Z")

</div>

Hey @coda

Thanks for posting on the Zoom Devforum! I am still learning, but I will try my best to help answer your question. 🙂

Checkout this related thread that may have the answer you are looking for:

> [@Got Request Body should be a valid JSON object error while create a meeting](https://devforum.zoom.us/t/-/7037):
>
> POST https://api.zoom.us/v2/users/51285889/meetings with the following request payload. { "topic": "Ronald & Panda: Spanish", "type": 2, "start\_time": "2019-12-11T10:35:01", "duration": 60, "timezone": "Asia/Shanghai", "password": "password", "agenda": "Agenda", "recurrence": { "type": 1, "repeat\_interval": 1, "weekly\_days": [1,2,3,4,5,6], "end\_times": 50 }, "settings": { "host\_video": true, "participant\_video": true, "cn\_meeting": true, "in\_m…

If this thread did not help, please let us know by replying back here and someone from the Developer Relations team will get back to you shortly.

Thanks,  
DeveloperBot

---

<div class="post-metadata">

**Author:** ![coda](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/coda/32/6871_2.png) [@coda](https://devforum.zoom.us/u/coda)\
**Post date:** [August 28, 2020, 2:48pm UTC](https://devforum.zoom.us/t/not-a-valid-json-object/28451/3 "2020-08-28T14:48:41Z")

</div>

The suggested link didnt help, thanks.  
But I may have a solution. I was sending the JSON in string form, which is sometimes acceptable in API scenario’s. It seems that if I send as a JSON object, the above code may work.

---

<div class="post-metadata">

**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:** [September 2, 2020, 6:19pm UTC](https://devforum.zoom.us/t/not-a-valid-json-object/28451/4 "2020-09-02T18:19:57Z")

</div>

Hey @coda,

Yes, the Zoom API is expecting the request body in JSON format. 🙂

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [October 3, 2020, 4:20am UTC](https://devforum.zoom.us/t/not-a-valid-json-object/28451/5 "2020-10-03T04:20:10Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.