We are introducing an update to ensure greater consistency between users’ account settings and API behavior. This change affects how certain fields in the Create a Meeting and Create a Webinar APIs apply default values when those fields are not explicitly included in the request body.
What’s Changing
Previously, some fields did not consistently inherit a user’s configured default settings when omitted from the API request. With this update, those fields will now automatically apply the user’s default settings whenever they are not provided in the request body.
The following fields will now inherit the user’s default settings when not included in the request body:
- watermark
- question_and_answer
- auto_start_meeting_summary
- who_will_receive_summary
- auto_start_ai_companion_questions
- who_can_ask_questions
- summary_template_id
- allow_host_control_participant_mute_state
- language_interpretation
- sign_language_interpretation
The following fields will now inherit the user’s default settings when not included in the request body:
- password
- add_watermark
- add_audio_watermark
- language_interpretation
- sign_language_interpretation
- panelist_authentication
- allow_host_control_participant_mute_state
Previously, these did not consistently inherit account defaults. This update improves consistency with UI behavior and ensures defaults are always applied when fields are not explicitly defined.
Exception:
The default_password field is not affected and remains unchanged.
No action required if your integration already specifies field values in the request body.
What You Need to Do
Please review your existing integrations to ensure they account for this behavior, especially if you rely on default values being applied manually in your application logic.
If you have any questions or feedback about this change, feel free to reply to this thread.