We have a web app that creates meetings for our customers using their zoom account. We create scheduled meetings (type 2)
We have a specific customer whose meetings are created with a password but the response payload from the API is returned without a password and the url to connect also does not contain the password. Only when actually trying to connect to the meeting is the password required but we dont know it.
The customer has shown us that his account security settings require a password for all meetings.
According to your latest announcement in https://marketplace.zoom.us/docs/guides/stay-up-to-date/announcements#passcode-and-wr-changes it is possible his settings are in the scenario #6, but the document does not state whether the password is autogenerated in this case.
Which App Type (OAuth / Chatbot / JWT / Webhook)?
Thanks for sharing that. In taking a look at the host’s account, it appears that their meeting settings are such that a meeting passcode would not be provided in the API response. I believe this scenario is covered in Scenario 5 in our API Behavior Chart here:
However the situation here seems to be different than the expected result, since while we do not get the password in the API response, and the join link does not contain it either, when trying to connect to the meeting it does require a password (which we do not know…)
Is it possible that the password is applied for the meeting but simply not returned in the response? If so would calling the GET endpoint for the meeting retrieve the password?
Thanks so much for clarifying that, and my apologies for not catching that before. Is it possible to share a screenshot of the password being required for this meeting (87613749994) when a user goes to join?
This is actually by design if the passcode required setting is not locked at the account level, or if the waiting room required setting is locked at the account level. We do have a feature request in our backlog for an option to have the Create Meeting API automatically generate the passcode. (ZOOM-201605)
As far as I could understand from the API documentation, the scenario you are describing should lead to the meeting being created WITHOUT a password (and then it is obviously not going to be in the API response), but what we are experiencing is different - meetings are created WITH a password (user is prompted for password when connecting via join url), but the password is not included in the API response (not in the url or on its own), so the user can’t login… Is this behaviour by design?
After checking with our team, this is expected behavior. Even if you provide a valid password value when creating a meeting in this scenario, it will not be returned. That said, I understand the issue this creates, and as Tommy mentioned, we do have a feature request in for this.