PUT /v1/config/monitoring/{id}

Update a watchdog rule's configuration — every field is optional and only sent fields change

Updates a watchdog rule. The body accepts the same fields as create, but every field is optional — only the fields you send are changed.

Authentication

API key with config:write permission. Project-scoped or tenant-scoped (with X-Project-Id).

Endpoint

PUT /v1/config/monitoring/{id}

Path parameters

Param	Type	Notes
`id`	UUID	The rule id

Request body

Any subset of the create-rule fields. Omitted fields are left unchanged.

{
  "intervalMinutes": 5,
  "spikeMultiplier": 4.0,
  "isEnabled": true
}

Response

200 OK

{
  "success": true,
  "data": {
    "updated": true
  }
}

Error responses

Status	`error.code`	When
400	`VALIDATION_ERROR`	`id` is not a UUID, or a body field failed validation
401	`UNAUTHORIZED`	Missing or invalid API key
403	`FORBIDDEN`	Key lacks `config:write`
404	`NOT_FOUND`	No rule with that id in your tenant

Example

curl -X PUT https://api.sigsentry.com/v1/config/monitoring/wdg_a1b2 \
  -H "Authorization: Bearer ss_secret_..." \
  -H "Content-Type: application/json" \
  -d '{ "isEnabled": false }'

To flip a rule on or off without touching anything else, send just { "isEnabled": true } or { "isEnabled": false }. The project-wide master switch lives in the dashboard at Project → Watchdog → Settings.