Update backup service

View as MarkdownOpen in Claude
Changes how ONE website is backed up. Send only what changes (at least one field); answers **200** with the backup service document, its attributes reading back under the same keys this body accepts. **Body** (JSON), every field optional: - `status` (`enabled`, `disabled`) - enables or pauses the website's automatic copies. - `preset` (integer) - id of another backup global configuration to move the website to. The website keeps its status, and the copies it already holds take the new configuration's retention. - `filesystem` (`default`, `custom`) and `content.included` (array) - what is copied. `content.included` must be sent together with `filesystem`: `default` accepts `core` and `database`; `custom` accepts `database`, `core`, `plugins`, `themes`, `mu_plugins`, `content` and `uploads`. Changing the areas keeps the exclusions the website has. Changing the `filesystem` resets them to the defaults of the new mode (and the areas too, unless you send them), because the exclusions of one mode do not apply to the other. Exclusions are managed in the dashboard: sending `content.excluded` answers 422. The schedule belongs to the configuration: sending `schedule` answers 422. Requires a full-access token (read-only tokens answer 403). A backup service or a configuration of another organization answers 404.

Authentication

AuthorizationBearer

Personal access token created in the Modular DS dashboard; read-only tokens can only call GET endpoints.

Path parameters

site_preset_backupstringRequired

Request

This endpoint expects an object.
contentobjectOptional
filesystemstringOptional
statusstringOptional

Response

200 - Backup service updated

dataobjectOptional
jsonapiobjectOptional