I’m creating meetings with the api and have been passing registrants_email_notification as false under the settings property but it seems to have no effect.
Hi @okzoomer if you send "registrants_email_notification": false (lowercase boolean value), this should return the correct response. Can you try this and check back to validate?
@michael.zoom this is getting sent as a lowercase boolean value ultimately, the code snippet is written in python/django and ultimately gets sent as proper json. Could there be another issue?
After creating a meeting with the correct settings (and setting both booleans to false), the values are as I want them to be (false), but on the meeting page it’s still shown that emails are activated and emails are sent if I register a participant. Using the update endpoint afterwards does not change anything! The values are set as I want them to, but emails are still always sent after registering participants.
I’d appreciate help since I have to disable all emails to registrants!
I am trying to disable the confirmation emails after registration . I am creating the meeting ( setting boolean to false) and then using the update endpoint to set it again to false but it didn’t work .
Any workaround for this ? I ve seen that the problem is there since 2020 was raised many times . I hope there is a fix for that
I’m seeing the same thing, and we don’t use webinar. Are there other settings that affect this per meeting setting? What we’re trying is to PATCH the meeting/123456789 with {‘settings’: { ‘registrants_confirmation_email’}, but when reading the meeting back, we’re gettingregistrants_confirmation_email is fixed to true. We don’t use/need registrations at all, but our backend thinks it needs to update the meeting i Zoom:
0) let’s check the settings for a meeting and verify that the actual settings match the wanted settings
read GET message/, it says this setting is true
compare actual value in Zoom (true) with wanted value (false), and if different do the next step
patching the setting to False gives 204 back
Now that we’ve modified the meeting, start over at 0. It becomes an endless loop.
Is this behavior still an issue for you? If so, can you share the endpoints you are using to patch the meeting invite and the response once it is patched? Have you tested making updates to different properties? I’d also double-check the account settings to ensure they are not causing the default value to remain unchanged.