---
title: API: config changes now carry through to your alert rules
description: Adding a keyword or an expected value to an existing monitor through the API or MCP changed what was checked, but no alert was set up. Removing one left the…
canonical: https://watchfor.io/changelog/2026-11-19-api-config-alert-rules-follow
---

[All updates](/changelog/page/2#2026-11-19-api-config-alert-rules-follow) 🐛 Fixed API MCP Nov 19, 2026 · v 13.3.7

# API: config changes now carry through to your alert rules

Adding a keyword or an expected value to an existing monitor through the API or MCP changed what was checked, but no alert was set up. Removing one left the alert switched on with nothing to judge. Now the matching alert is created or switched on and off with the value, as the dashboard card does. Resetting the confirmation count or duration with null puts the rules back on the defaults, and an empty notification group list really stops notifications.

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-11-19-api-config-alert-rules-follow · Site guide: https://watchfor.io/llms.txt
