Account settings not covered by API


“Mute Participants on Entry” is one example of an account setting that is not included in responses for /accounts/{accountId}/settings.

The account API should cover all configurable settings so that the API can be relied upon for configuration management and compliance testing.

Are there plans to achieve parity between web settings and API settings?

Hey @nickmel,

Yes, we do plan to have feature parity between web and API settings, but some settings we have not implemented yet.

I will get an idea of when we can add this setting to the API. (ZOOM-174903)