Update a website's Malware Scanner settings

Changes how one website is scanned. Send only the fields you want to change, and at least one.

The schedule and content.excluded are not edited here: the schedule comes from the global configuration and exclusions are a dashboard-only setting. Changing filesystem always resets the exclusions to the new mode’s default, and resets the scanned areas too unless you send content.included in the same request.

Body

• status (enabled or disabled, optional): turns scanning on or off.
• preset (integer, optional): id of another Malware Scanner global configuration to move the website to (ids come from “List Malware Scanner global configurations”). The website keeps its status. Moving a website to a premium configuration adds it to the premium tier, which is metered per website and per month, with no websites included in the plan. To assign many websites to one configuration at once, always switching them on, use “Assign websites to a Malware Scanner global configuration” instead.
• filesystem (string, optional): which areas are scanned. It is valid on its own.
• content.included (array of strings, optional): the areas to scan; it requires filesystem in the same request.

Errors

• 404: preset belongs to another organization.
• 409: status is enabled on a website that is paused and not yet registered with the scanning provider. A website the assignment already switched on keeps accepting status: enabled while its registration runs.
• 409: preset is a premium configuration and the organization has not subscribed the premium Malware Scanner add-on. The user subscribes it from the Modular DS dashboard and the same request then goes through; an integration never buys it. The message reads “The premium Malware Scanner add-on must be active to use a premium global configuration.”
• 422: no field is sent (the message is “Send at least one field to update: status, preset, filesystem or content.”), content.excluded or schedule is sent, or preset is not a Malware Scanner configuration.