Turn daily storage backups on or off

set_storage_backup_schedule

Turns the automatic daily storage backup of a site on or off, the same as the Daily backups switch in Storage configuration.

POST /v1/set_storage_backup_scheduleScopesites:writeMakes changes

It only controls the archive the platform takes each night. With it off, the nightly run skips the site and takes no new automatic storage backup until it is turned back on. Manual backups with create_storage_backup still work either way, and every archive the site already holds stays, still listed and still thinned as it ages, so turning it off deletes nothing.

Daily storage backups are on for every site until someone turns them off, and they only ever run for a workspace on a paid plan, so turning them on for a free workspace changes nothing until the plan is paid. Any member of the workspace can change the setting, and the response carries enabled with the setting as it now stands.

The tool tells the client to change it only when you ask, and to say plainly that with it off no new daily archive of your files is taken. See Turn daily storage backups off.

Request

Call it with a POST to https://api.modulify.ai/v1/set_storage_backup_schedule, sending the inputs below as a JSON object. The token needs the sites:write scope.

It makes changes, so send an Idempotency-Key header whenever you might retry it. A retry with the same key gets the first answer back instead of running again.

curl -X POST https://api.modulify.ai/v1/set_storage_backup_schedule \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"projectId":"PROJECT_ID","enabled":true}'

Over MCP, the same method is the set_storage_backup_schedule tool.

Inputs

Input	Type	Required	Description
`projectId`	string	Yes	The site whose daily storage backup should be turned on or off.
`enabled`	boolean	Yes	True to take the automatic daily storage backup, false to stop taking it.

Response

Every call answers with the JSON envelope of success, message, data, code and version. data holds the result described above, and on a method that returns a total, count carries it. The response headers carry the call's X-Request-Id and what is left of your per-minute budget in X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Errors explains every status code a call can answer with.