Monitors
- Create a monitor with a URL, an optional CSS selector, a schedule and a sensitivity level (full API).
- List monitors with their status, schedule and last check time.
- Update, pause or delete a monitor (full API).
Website change monitoring API for your own tools
Alerts in email and Slack cover most teams. When changes need to flow into a CRM, a data warehouse, a pricing engine or a ticket queue, use the WebsiteChange website change monitoring API. It gives your systems the same monitors, versions, diffs and AI summaries you see in the app, and webhooks push each change to you the moment it is found.
API access on each plan
| Plan | API access |
|---|---|
| Starter | no API |
| Growth | read API |
| Business | full API |
| Enterprise | full API with higher rate limits |
The read API lets you pull monitors, versions, diffs and summaries into your own reports. The full API adds creating, updating, pausing and deleting monitors, so you can manage hundreds of pages from code. Enterprise keeps the same endpoints with higher rate limits for large watchlists and frequent syncs. Webhooks come with Growth and every plan above it.
What the API covers
The API is a JSON REST interface. Every call is scoped to one workspace.
Versions
- List the versions of a monitor with their dates and importance scores.
- Fetch one version with its text, page title, links and screenshot address.
Diffs and summaries
- Fetch the text diff between a version and the one before it, or between any two versions of the same monitor.
- Fetch the AI summary and importance score of a change.
- Filter changes by date range, importance or monitor, for example all high importance changes this week.
Calls to read versions and diffs do not use checks or AI summaries. Creating a monitor through the API uses the same page and check limits as creating it in the app.
Webhooks for every real change
Instead of polling, register a webhook address in the workspace settings. When a check finds a real change that passes your importance filter, WebsiteChange sends an HTTPS POST with a JSON body to your endpoint. The payload carries these fields:
Each delivery is signed with a secret from your workspace settings, so your endpoint can confirm that the request came from WebsiteChange. Failed deliveries are retried, and the delivery log shows every attempt and the status your endpoint returned. Webhooks follow the same importance filters and routing as other channels on the website change alert page.
- monitor_id, the identifier of the monitor that found the change,
- url, the address of the watched page,
- checked_at, the date and time of the check in UTC,
- importance, low, medium or high,
- summary, the one-line AI summary of the change,
- diff_url, a link to the full text and visual diff in the app,
- screenshot_url, a link to the screenshot of the new version.
API keys per workspace
API keys are created in the workspace settings by a workspace admin.
On Business and Enterprise, key creation and revocation appear in the audit log together with the seat that made the change.
- Each key belongs to one workspace and sees only its monitors and history.
- Agencies give each client workspace its own key, so one integration never touches another client's data.
- You can create several keys per workspace, for example one for a dashboard and one for a pricing script.
- Rotate or revoke a key at any time. A revoked key stops working immediately.
What teams build with it
A pricing team pulls high importance changes from competitor product pages into its pricing engine every 15 minutes and reviews the suggested response.
A revenue operations team sends webhook payloads about new job openings at target accounts into its CRM, attached to the account record.
A compliance team stores every summary and diff link from regulator pages in its own case system for audits.
An agency builds a client portal that lists the latest changes per client, using one key per workspace.
A data team loads versions and summaries into its warehouse each night to report on how competitors change pricing and positioning over time.
For the mechanics behind each record, see website change detection, ai website monitoring and website archive tools.
The same rules apply through the API
Monitors created by API follow the same rules as monitors created in the app. We only read publicly reachable pages, respect robots.txt, never log in on your behalf, never solve CAPTCHAs and never bypass paywalls or access controls. Requests to the same host are spaced out politely, whatever schedule you set in code.
Website change monitoring API questions
Growth includes the read API. Business includes the full API. Enterprise includes the full API with higher rate limits. Starter does not include API access.
monitor_id, url, checked_at, importance, summary, diff_url and screenshot_url, sent as JSON in an HTTPS POST to your endpoint.
No. Each key belongs to one workspace. Create a separate key in each workspace you want to connect.
Reading monitors, versions, diffs and summaries does not. Monitors you create through the API use checks and summaries exactly like monitors created in the app.
Connect your first monitor
Paste a public URL to see the snapshot and summary your API will return, then pick a plan with API access. No card needed for the demo.