# Zoom V2 API returning XML from create\_meeting endpoint? **URL:** \ **Category:** API and Webhooks\ **Created:** [August 24, 2020, 6:55pm UTC](https://devforum.zoom.us/t/zoom-v2-api-returning-xml-from-create-meeting-endpoint/28003 "2020-08-24T18:55:00Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![elyes](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elyes/32/9007_2.png) [@elyes](https://devforum.zoom.us/u/elyes)\ **Post date:** [August 24, 2020, 6:55pm UTC](https://devforum.zoom.us/t/zoom-v2-api-returning-xml-from-create-meeting-endpoint/28003/1 "2020-08-24T18:55:01Z")
**Description** I was under the impression that the V2 Zoom API was a JSON API. Users of our application were running into issues this morning, and it turns out that it’s because the back-end library we use to make HTTP requests was crashing when attempting to parse response bodies into JSON. After logging what the response was, we observed the response body to look like: ` 300Validation Failed.passwordPassword provided does not match the password requirement settings set for this account. The password must follow these rules: [Password must contain only numeric characters.].` Why is the response coming through as XML from the V2 create\_meeting endpoint? Did the wires get crossed between the V1 and V2 APIs? **Error** JSONDecodeError **Which App Type (OAuth / Chatbot / JWT / Webhook)?** JWT app **Which Endpoint/s?** [Create meeting](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate) **How To Reproduce (If applicable)** Steps to reproduce the behavior: 1. Make a request to the V2 create meeting endpoint that does not meet the password requirements for the Zoom user in question 2. Get an XML response ---
**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:** [August 26, 2020, 5:15pm UTC](https://devforum.zoom.us/t/zoom-v2-api-returning-xml-from-create-meeting-endpoint/28003/2 "2020-08-26T17:15:07Z")
Hi @elyes, Can you please send us a sample request that returned this error? If it contains any private information, can you please send it to [developersupport@zoom.us](mailto:developersupport@zoom.us) ? ---
**Author:** ![sardar.chayan](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sardar.chayan/32/10385_2.png) [@sardar.chayan](https://devforum.zoom.us/u/sardar.chayan)\ **Post date:** [August 28, 2020, 6:09am UTC](https://devforum.zoom.us/t/zoom-v2-api-returning-xml-from-create-meeting-endpoint/28003/3 "2020-08-28T06:09:33Z")
Hi, I am facing the similar issue when I tried to use Create Meeting API endpoint with an invalid password **Endpoint** : [Create Meeting](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate) **Scenario** : Entered password having less than 8 characters. **Headers:** _Content-Type:application/json_ **Request Body** : { “topic”: “Test My Meeting” ,“start\_time”: “2020-08-28T12:00:00Z” ,“duration”: “60” ,“timezone”: “Asia/Calcutta” ,“password”: “1234567” ,“agenda”: “Discussion about Me” ,“settings”:{ “use\_pmi”:false, “approval\_type”: 0 ,“registrants\_confirmation\_email”: “true” ,“registrants\_email\_notification”: “true” } } **Response:** **Header:** _Content-Type: application/xml;charset=UTF-8_ **Response Body** : \ `300` Validation Failed. password Password provided does not match the password requirement settings set for this account. The password must follow these rules: [Password must have a minimum length of 8 characters.]. ---
**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:** [August 31, 2020, 6:00pm UTC](https://devforum.zoom.us/t/zoom-v2-api-returning-xml-from-create-meeting-endpoint/28003/4 "2020-08-31T18:00:04Z")
Hi @sardar.chayan, Can you please provide the following in your request headers? accept: application/json This should resolve the issue. ---
**Author:** ![sardar.chayan](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sardar.chayan/32/10385_2.png) [@sardar.chayan](https://devforum.zoom.us/u/sardar.chayan)\ **Post date:** [August 31, 2020, 6:27pm UTC](https://devforum.zoom.us/t/zoom-v2-api-returning-xml-from-create-meeting-endpoint/28003/5 "2020-08-31T18:27:53Z")
Thanks @ojus.zoom This did the trick 🙂 Well previously it did work without this header. I presume there were some changes in the latest Zoom API upgrades. ---
**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\ **Post date:** [September 2, 2020, 9:26pm UTC](https://devforum.zoom.us/t/zoom-v2-api-returning-xml-from-create-meeting-endpoint/28003/6 "2020-09-02T21:26:15Z")
Hey @sardar.chayan, Glad to hear it’s been sorted! Let us know if anything else pops up. (and thanks @ojus.zoom!) Best, Will ---
**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, 7:26am UTC](https://devforum.zoom.us/t/zoom-v2-api-returning-xml-from-create-meeting-endpoint/28003/7 "2020-10-03T07:26:17Z")
Closed on October 3, 2020, 7:26am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.