Retrieve a Monitor
Fetch a monitor’s full configuration, status, schedule, and current baseline by ID.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Response
Monitor
A web monitor. mode is the constant web; behavior is described by target (page/sitemap/extract) and change_detection (exact/semantic).
Top-level monitor category. Always web today; the concrete behavior is described by target and change_detection.
web "mon_123"
"Acme pricing monitor"
Discriminated union describing what the monitor watches.
- Page target
- Sitemap target
- Extract target
Discriminated union describing how changes are detected.
- Exact
- Semantic
Discriminated union describing how the monitor is scheduled. Only interval is supported today; cron and exact_time are reserved for future use.
Monitor lifecycle status. failed means the most recent run failed (see the monitor's last_error); failed monitors keep running on schedule and flip back to active on the next successful run. Monitors are auto-paused after repeated consecutive failures or insufficient-credit skips; resume by PATCHing status to active.
active, paused, failed When the next scheduled run is due.
Error from the most recent failed run; null when the last run succeeded.
User-defined tags for grouping and filtering monitors and their changes.
201 - 50["pricing", "competitor"]Current baseline: the last observed value the monitor compares new snapshots against. Its shape follows target.type (page/sitemap/extract). Only populated on GET /monitors/{monitor_id}; null until the first baseline run completes (and after a target or change_detection update, which resets the baseline).
- Page baseline
- Sitemap baseline
- Extract baseline