Week of September 26–October 2, 2026
Validate live answers against what they actually cite 🔥
API Monitors can now correlate with UI Monitor sessions: when a live browser session makes a request your Monitor is watching for, it gets checked against your test suite's real assertions using the actual captured request and response — not a synthetic stand-in. The whole thing runs off the same lightweight snippet UI Monitor already uses to watch your pages, so there's no server-side instrumentation or backend changes required to get there — point LitmusLab at the traffic you want checked, and it's checked.
It goes further, too: a check can continue into a second, real API call after the first one matches. The case this unlocks — verify that a live chat answer actually matches the document it cited, by having the check fetch that real document and compare, all triggered by one real user interaction. No scripted test, no synthetic data — just your actual production traffic, validated as it happens.
Fixes worth knowing about
Monitor Constants (your environment-style values, like an API hostname) now correctly apply wherever a Monitor check makes a real API call — previously they were only used in a couple of narrower cases, so a constant-based URL could silently fail to resolve. Extracting a value from a request or response's headers (not just the body) is also now supported in test suite steps. And we removed a "pass rate" column from Monitor results that could only ever show 0% or 100% for live traffic — it wasn't telling you anything a plain pass/fail didn't already.