Monitors scrape a public page on a schedule and record meaningful content changes. The first successful check establishes a baseline and does not send a notification.
Create a monitor
If the response includes a webhookSecret, store it immediately. PagePith returns generated webhook secrets only once.
Monitor lifecycle
- List monitors to inspect current state.
- Pause or resume a monitor with an update request.
- Run a monitor immediately when you need an unscheduled check.
- List checks for execution history.
- List events for detected changes.
- Delete a monitor when you no longer need it.
Each check that performs a successful scrape consumes usage according to your plan. See the monitoring endpoints for complete schemas.