1
Create
POST /monitor with what to watch, how often, and optionally a goal that describes which changes matter.2
Baseline
The first check records every page. Nothing is announced, because every page is new.
3
Check
Each scheduled check fetches every page again and marks it
same, new, changed, removed or error, with a diff.4
Get told
Changes that match your goal are posted to your webhook and emailed to your addresses. You can also read any check with
GET /monitor/{id}/checks/{checkId}.Example request
This monitor watches a competitor’s pricing page for price changes and their changelog for new posts, every weekday morning:Example response
201 Created. Keep the webhook.secret: you need it to verify each webhook. You can read it again with GET /monitor/{id}.
To take the baseline straight away instead of waiting for the schedule, call POST /monitor/{id}/run.
The parts of a monitor
Targets
Fixed pages, a whole site section, or a web search.
Schedules
Plain phrases or cron, in any timezone.
Detecting changes
Text diffs, tracked JSON fields, and how to cut noise.
Goals and judging
One sentence that decides which changes you hear about.
Alerts
Webhooks and email.
Limits and credits
What a check costs, and what each plan allows.
Credits
Creating, reading and changing a monitor is free. Each check costs 1 credit per page fetched, plus extra forjson extraction, search targets and judging. See Limits and credits.
Monitors need a direct Prefetch API key. They aren’t available through RapidAPI, which bills from a response header, and a scheduled check runs when there’s no response to carry one.