Enable or disable a scheduled job

toggle_site_cron

Turns one scheduled job on a site on or off.

POST /v1/toggle_site_cronScopeconfig:writeMakes changes

Disabling stops it firing but keeps its definition and history. Enabling recomputes the next run from that moment and clears both the consecutive failure count and any reason the platform switched it off automatically. See Scheduled jobs.

Request

Call it with a POST to https://api.modulify.ai/v1/toggle_site_cron, sending the inputs below as a JSON object. The token needs the config: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/toggle_site_cron \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"projectId":"PROJECT_ID","cronId":"CRON_ID","enabled":true}'

Over MCP, the same method is the toggle_site_cron tool.

Inputs

Input	Type	Required	Description
`projectId`	string	Yes	The site id.
`cronId`	string	Yes	The job id from `list_site_crons`.
`enabled`	boolean	Yes	True to enable the job, false to disable 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.