Miss one field on the account settings API

Not only account lock settings but also account settings API don’t have this field (schedule_meeting.require_password_for_instant_meetings) data, and we would like to know how to get this value via Zoom API properly. :thinking:

Which App Type (OAuth / Chatbot / JWT / Webhook)?

OAuth App

Which Endpoint/s?

How To Reproduce (If applicable)

curl --location --request GET 'https://api.zoom.us/v2/accounts/me/settings' \
--header 'Authorization: Bearer [access-token]' 
    "schedule_meeting": {
        "host_video": true,
        "participant_video": true,
        "audio_type": "both",
        "join_before_host": true,
        "personal_meeting": false,
        "use_pmi_for_scheduled_meetings": true,
        "use_pmi_for_instant_meetings": true,
        "enforce_login": false,
        "enforce_login_with_domains": false,
        "enforce_login_domains": "",
        "not_store_meeting_topic": false,
        "force_pmi_jbh_password": false,
        "require_password_for_scheduling_new_meetings": false,
        "require_password_for_pmi_meetings": "none",
        "embed_password_in_join_link": true,
        "mute_upon_entry": false,
        "jbh_time": 0


Hey @ylu,

Thank you for reaching out to the Zoom Developer Forum. Have you tried setting that field first to see if it is returned by the Get Account Settings API? Do you have a Free account or a Pro account with a single host?


Hi Max,

Yes, we have updated the field (require_password_for_instant_meetings) on the account settings a few times, but we still can’t get this data on the API response. We use the business account with OAuth App to test this API.

curl --location --request GET 'https://api.zoom.us/v2/accounts/me/settings?custom_query_fields=require_password_for_instant_meetings' \
--header 'Authorization: [access-token]'
    "schedule_meeting": {}


Hey @ylu,

Thank you for confirming. Please send an email to developersupport@zoom.us with a link to this thread.

In that email, please provide your account number and I’ll work to reproduce this issue before reaching out to our engineering team.


1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.