Cannot update user settings (email notifications)


Same issue as Unable to update user settings with API and Unable to update user settings (closed without being resolved).
And also same as Cannot update user settings (some obscure fix this is likely similar to what I need).

Assuming I’m missing an undocumented param like in the last link but please lmk if you know what it is.

Thanks for any help you can provide!

I’m calling
with json: {“email_notification”: {“cloud_recording_available_reminder”: false}}
and headers: {“Authorization”: “Bearer XYZABC”, “Content-Type”: “application/json”}

And I get a 204 response but the settings are not updated in the UI or if I call

No error message but the settings are not updated.

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

Which Endpoint/s?

How To Reproduce (If applicable)
See above

Screenshots (If applicable)

Additional context

Hi @chou,

Can you make sure your request URL includes the following query param:

Let me know if this resolves the issue, thanks!

1 Like

Hey Will,

Thanks for the quick reply! I change my PATCH call to

but it’s still not updating the email_notification.cloud_recording_available_reminder field.

Any other suggestions?

Hi @chou,

You will also ned to ensure you’re passing the request body, as well as the query parameter. Are you passing both?


Hi @will.zoom,

Yup I’m passing the json body {“email_notification”: {“cloud_recording_available_reminder”: false}}

Actually now that I look at the query parameter you suggested of option=recording_authentication why am I supposed to pass that? I want to turn off email notifications for cloud recordings, which is in the first schema listed here not one of the schemas that goes with an option.


Hey @chou,

After some further testing on my end, this seems like it may be a bug. I’ve shared these examples with our Engineering team for further investigation and I’ll follow up here directly shortly. (ZOOM-316410)


Great thanks @will.zoom!

Hey @chou,

Confirming this is a bug—we’re working on a fix for our next release, which should be in the next couple of weeks. I’ll be happy to update back here once the fix has been released.


Awesome thanks @will.zoom!

Hi @chou,

Our team confirmed this is a bug. We’re working on a fix to be included in our next release in a couple of weeks. We’ll follow up here once released.

Thanks again for raising it,

No worries thanks @will.zoom!

Thanks, we’ll follow up here once this is released :slight_smile:

Thanks @will.zoom. (Just commenting so this thread doesnt get closed)

Thanks @chou! We’re almost there. :slight_smile:

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