Snag Watcher

API reference

List runs

GET /v1/watchers/{id}/runs

This lists every check a watcher ran, newest first, and why it fired or didn't. summary says what happened in one sentence. sites has what each site returned and, for each condition, how many results it held for, failed for or couldn't tell. due_at is when the check was planned and late_seconds is how late it ran. Both are null on older checks.

Query
limit1 to 100, default 20. Values outside it are clamped
cursornext_cursor from the previous page. It's null on the last page, and a bad one is 400 invalid_request
Shell
curl "https://api.watcher.manwhas.shop/v1/watchers/wch_dhjqcvaqnhrchsnv7gtc/runs?limit=1" -H "Authorization: Bearer $SNAG_KEY"
JSON
{
  "data": [
    {
      "run_at": "2026-11-10T14:00:03.120Z",
      "due_at": "2026-11-10T14:00:00.000Z",
      "late_seconds": 3,
      "fired": false,
      "events": [],
      "summary": "Didn't fire: price <= 100 was false.",
      "sites": [
        {
          "site": "sweetwater.com",
          "url": "https://www.sweetwater.com/store/detail/SM58--shure-sm58-cardioid-dynamic-vocal-microphone",
          "outcome": "ok",
          "candidates": 1,
          "matched": false,
          "conditions": [{ "condition": "price <= 100", "held": 0, "failed": 1, "unknown": 0 }],
          "issues": [],
          "detail": null
        }
      ]
    }
  ],
  "next_cursor": "2026-11-10T14:00:03.120Z"
}
summary starts withMeans
FiredIt sent matched or changed
Couldn't readEvery site failed, so nothing was checked. The sites and their outcomes are named
Matched, waitingnotify.confirm is waiting for the next check
Matched, but you were already toldIt matched, but repeat or cooldown held the event back
Nothing on the page fit the targetWe read the page, but nothing matched target
Didn't fireNames the condition that was false, or the field the page didn't show