Connect website monitoring to the systems you already run. Use the API to manage monitors and read evidence, or receive matching changes at your own webhook endpoint.
Pro & Business · Scoped API tokens · Signed webhook events
{
"type": "monitor.changed",
"monitor": {
"name": "Vendor pricing"
},
"change": {
"before_excerpt": "Basic costs $24",
"after_excerpt": "Basic costs $18"
}
}Verify the signature, deduplicate the event, then decide what your system should do.
Illustrative payload excerpt. The reference documents the full envelope, signatures and delivery identifiers.
List and manage supported monitors, load cloud previews, read retained changes and inspect usage. Request an immediate check and retrieve its receipt when your workflow needs one.
The API uses the same workspace permissions, capture engine and plan allowances as PageFluxer’s web app.
API endpoints & authentication →Send change events to your own HTTPS receiver. Include the event in an internal review queue, enrich a report, or trigger an automation you control.
Verify the signature and process stable event IDs once. Temporary delivery failures retry; an ambiguous response can result in a duplicate.
Payloads, signatures & retries →Connect an existing catalogue or research list to supported monitor creation. A successful cloud preview establishes the starting capture.
Read retained before-and-after content, change metadata and saved summaries. Use the history your workspace actually captured.
Let your receiver decide which internal system should act on a matching change. No email notification is required for webhook delivery.
No. You can create a monitor on the website and configure webhook delivery. API access and webhook delivery are separate capabilities included with Pro and Business.
No. Monitor, capture, preview, history and manual-check allowances still apply. API requests and outbound attempts also have their own limits, documented in the guides and usage page.
Yes. PageFluxer retries eligible temporary failures, and a response can be lost after your receiver processed an event. Verify each request and deduplicate event IDs before running an action.
For a compatible assistant, start with the MCP integration. It provides scoped OAuth access and tools designed for monitor previews, creation and retained evidence. Use the REST API for software you control.
Start with a working example, then use the references for the details.