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?
Which App Type (OAuth / Chatbot / JWT / Webhook)?
How To Reproduce (If applicable)
Steps to reproduce the behavior:
- Make a request to the V2 create meeting endpoint that does not meet the password requirements for the Zoom user in question
- Get an XML response
Can you please send us a sample request that returned this error? If it contains any private information, can you please send it to email@example.com ?
I am facing the similar issue when I tried to use Create Meeting API endpoint with an invalid password
Endpoint: Create Meeting
Scenario: Entered password having less than 8 characters.
“topic”: “Test My Meeting”
,“agenda”: “Discussion about Me”
Header: Content-Type: application/xml;charset=UTF-8
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
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.].
Can you please provide the following in your request headers?
This should resolve the issue.
This did the trick
Well previously it did work without this header. I presume there were some changes in the latest Zoom API upgrades.
Glad to hear it’s been sorted! Let us know if anything else pops up. (and thanks @ojus.zoom!)
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.