# Password not being required when scheduling a meeting via API despite user setting

**URL:** <https://devforum.zoom.us/t/password-not-being-required-when-scheduling-a-meeting-via-api-despite-user-setting/18756>\
**Category:** API and Webhooks\
**Created:** [May 22, 2020, 4:05pm UTC](https://devforum.zoom.us/t/password-not-being-required-when-scheduling-a-meeting-via-api-despite-user-setting/18756 "2020-05-22T16:05:52Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![mattpegler](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@mattpegler](https://devforum.zoom.us/u/mattpegler)\
**Post date:** [May 22, 2020, 4:05pm UTC](https://devforum.zoom.us/t/password-not-being-required-when-scheduling-a-meeting-via-api-despite-user-setting/18756/1 "2020-05-22T16:05:52Z")

</div>

**Description**  
When scheduling meetings via the API for users that have “Require a password when scheduling new meetings” enabled does not result in a password being required. We do not specify the password parameter when scheduling the meeting, but we’d expect a password to be auto generated due to the “Require a password…” user setting. Is this expected? An example meeting is 82529829258

---

<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:** [May 28, 2020, 10:53pm UTC](https://devforum.zoom.us/t/password-not-being-required-when-scheduling-a-meeting-via-api-despite-user-setting/18756/2 "2020-05-28T22:53:21Z")

</div>

Hey @mattpegler,

Please see the answer to your question here:

> [@Created type 2 meetings don't return password](https://devforum.zoom.us/t/created-type-2-meetings-dont-return-password/18211/5):
>
> Hey @InfoAdam, I just tested and the [Create Meeting API](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate) returned a password without me setting one in the request body. Here is my Account Level password settings (I am not using [PMI](https://support.zoom.us/hc/en-us/articles/203276937-Using-Personal-Meeting-ID-PMI-) for scheduled meetings): Request body: { "topic": "Test without setting password in api call with account level settings locked", "type": "2", "start\_time": "2020-06-08T10:00:00", "duration": "30" } Response body: { "uuid": "[redacted]", "id": 123456789, "ho…

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![mattpegler](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@mattpegler](https://devforum.zoom.us/u/mattpegler)\
**Post date:** [May 28, 2020, 11:10pm UTC](https://devforum.zoom.us/t/password-not-being-required-when-scheduling-a-meeting-via-api-despite-user-setting/18756/3 "2020-05-28T23:10:30Z")

</div>

It looks like the only difference here is that you have the setting locked while we do not. Is that still expected that a password is not required in that case?

---

<div class="post-metadata">

**Author:** ![michael.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael.zoom/32/37213_2.png) [@michael.zoom](https://devforum.zoom.us/u/michael.zoom)\
**Post date:** [June 2, 2020, 4:08pm UTC](https://devforum.zoom.us/t/password-not-being-required-when-scheduling-a-meeting-via-api-despite-user-setting/18756/4 "2020-06-02T16:08:17Z")

</div>

@mattpegler when the setting is not locked, the API is interpreting that a password is not provided intentionally.

---

<div class="post-metadata">

**Author:** ![mattpegler](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@mattpegler](https://devforum.zoom.us/u/mattpegler)\
**Post date:** [June 3, 2020, 12:14am UTC](https://devforum.zoom.us/t/password-not-being-required-when-scheduling-a-meeting-via-api-despite-user-setting/18756/5 "2020-06-03T00:14:02Z")

</div>

It still seems weird that a user with require\_password\_for\_scheduling\_new\_meetings enabled isn’t required to set a password when scheduling new meetings. We’ll change it on our side to help our customers, but I do think this is unexpected and flawed behavior.

---

<div class="post-metadata">

**Author:** ![mattpegler](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@mattpegler](https://devforum.zoom.us/u/mattpegler)\
**Post date:** [June 3, 2020, 5:36pm UTC](https://devforum.zoom.us/t/password-not-being-required-when-scheduling-a-meeting-via-api-despite-user-setting/18756/6 "2020-06-03T17:36:37Z")

</div>

Maybe consider renaming that setting to something like require\_password\_for\_scheduling\_new\_meetings\_except\_via\_the\_api

---

<div class="post-metadata">

**Author:** ![michael.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael.zoom/32/37213_2.png) [@michael.zoom](https://devforum.zoom.us/u/michael.zoom)\
**Post date:** [June 5, 2020, 11:21pm UTC](https://devforum.zoom.us/t/password-not-being-required-when-scheduling-a-meeting-via-api-despite-user-setting/18756/7 "2020-06-05T23:21:20Z")

</div>

> [@mattpegler](#):
>
> require\_password\_for\_scheduling\_new\_meetings\_except\_via\_the\_api

@mattpegler I think that would take the record for longest property name 🙃

Joking aside, I get the weirdness around this flow. We’re evaluating how to make this cleaner, but there were reasons we chose this initially in order to not unexpectedly break some key integrations and allow account settings to be overridden when not locked.

---

<div class="post-metadata">

**Author:** ![mattpegler](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@mattpegler](https://devforum.zoom.us/u/mattpegler)\
**Post date:** [June 9, 2020, 3:33pm UTC](https://devforum.zoom.us/t/password-not-being-required-when-scheduling-a-meeting-via-api-despite-user-setting/18756/8 "2020-06-09T15:33:51Z")

</div>

Supporting legacy users is always cumbersome. I get it.

The weirdness with this setting continues for us. If a user has use\_pmi\_for\_scheduled\_meetings enabled, it looks like we’ll clobber the existing password when we schedule new meetings. So any meeting URLs that have been sent out with the password embedded in the URL will not be valid because it looks like the user’s personal meeting room’s password gets changed.

---

<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:** [June 12, 2020, 10:51pm UTC](https://devforum.zoom.us/t/password-not-being-required-when-scheduling-a-meeting-via-api-despite-user-setting/18756/9 "2020-06-12T22:51:17Z")

</div>

Hey @mattpegler,

If the user is using PMI for scheduled meetings, and they require a password, it should not change the PMI password.

Thanks,  
Tommy

---

<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 21, 2020, 10:02pm UTC](https://devforum.zoom.us/t/password-not-being-required-when-scheduling-a-meeting-via-api-despite-user-setting/18756/10 "2020-08-21T22:02:17Z")

</div>

Closed on August 21, 2020, 10:02pm UTC


