Update a website's backup settings
Changes how one website is backed up. Send only the fields you want to change, and at least one.
Changing the areas keeps the exclusions the website has. Changing 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.
Body
status(enabledordisabled, optional): turns the website’s automatic backups on or pauses them.preset(integer, optional): id of another backup global configuration to move the website to. The website keeps its status, and the backups it already holds take the new configuration’s retention.filesystem(defaultorcustom, optional): which areas are copied.defaultcopies the WordPress files and the database as two areas and acceptscoreanddatabase;customlets you choose amongdatabase,core,plugins,themes,mu_plugins,contentanduploads.content.included(array of strings, optional): the areas to copy; it must be sent together withfilesystem.
Errors
- 422: no field is sent, or
content.excluded(exclusions are managed in the dashboard) orschedule(the schedule belongs to the global configuration) is sent.
Authentication
AuthorizationBearer
Personal access token created in the Modular DS dashboard; read-only tokens can only call GET endpoints.
Path parameters
site_preset_backup
Query parameters
include
Relations to add to the answer: preset (the global configuration the website uses) and last_backup (its last backup), comma separated. None by default. Any other name, including the camelCase lastBackup, answers 400.
Request
This endpoint expects an object.
content
filesystem
status
Response
200 - Backup service updated
data
jsonapi
Errors
400
Bad Request Error
