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:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><result><code>300</code><message>Validation Failed.</message><errors><field>password</field><message>Password provided does not match the password requirement settings set for this account. The password must follow these rules: [Password must contain only numeric characters.].</message></errors></result>
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
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 ?
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
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.].
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.