---
title: API: the keyword you set is the one that gets checked
description: Setting config.keywordValue on an HTTP monitor through the API or MCP answered 200, but the check kept looking for the old text. The keyword is now turned…
canonical: https://watchfor.io/changelog/2026-11-19-api-keyword-and-unknown-fields
---

[All updates](/changelog/page/2#2026-11-19-api-keyword-and-unknown-fields) 🐛 Fixed API MCP Nov 19, 2026 · v 13.3.6

# API: the keyword you set is the one that gets checked

Setting config.keywordValue on an HTTP monitor through the API or MCP answered 200, but the check kept looking for the old text. The keyword is now turned into the check exactly as the Response Body Match card does, on create and update, and a keyword that contradicts the regexp sent with it is a 400. Confirmation count, duration and notification groups changed in config now apply to every alert rule, and contacts and contact groups reject a field they don't know (contact_ids instead of contactIds) instead of ignoring it.

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-11-19-api-keyword-and-unknown-fields · Site guide: https://watchfor.io/llms.txt
