---
title: API fixes: keyword checks created through the API, and tags surviving a partial update
description: If you created an HTTP monitor through the API with a body keyword (failIfBodyNotMatchesRegexp, as the docs showed), every check failed with a parse error and…
canonical: https://watchfor.io/changelog/2026-09-04-api-keyword-and-tags-fixes
---

[All updates](/changelog/page/5#2026-09-04-api-keyword-and-tags-fixes) 🐛 Fixed Sep 4, 2026 · v 6.6.3

# API fixes: keyword checks created through the API, and tags surviving a partial update

If you created an HTTP monitor through the API with a body keyword (failIfBodyNotMatchesRegexp, as the docs showed), every check failed with a parse error and the monitor went down at once. That was our bug: the API accepted a plain string while the checker expected a list. Both shapes now work, and the Alerting tab shows the pattern for API-created monitors instead of an empty field. A second bug: a PATCH that changed only the config quietly erased the monitor's tags; omitted tags are now left alone. The docs also say how to alert on a keyword: a rule on http.body_regexp_match equal to 0.

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-09-04-api-keyword-and-tags-fixes · Site guide: https://watchfor.io/llms.txt