What DiffMon monitors and how it detects changes across web pages and JSON APIs.

Plan limits for monitors, intervals, retention, and webhook availability.

How long snapshots, diffs, and logs are stored, plus ways to keep payload storage predictable.

Monitor HTML pages for meaningful changes with normalized diffs and optional ignore rules.

Monitor JS-rendered pages with deterministic waits and rendered DOM diffs when simple fetch is not enough.

Track JSON responses for schema or value changes with structure-aware hashing.

How DiffMon classifies API diffs into schema vs value changes, with severity, fingerprints, and troubleshooting.

Use post-diff rules to suppress noise, route important changes, and escalate notification severity.

Email alerts with request IDs, throttling, and options for muted channels.

How incidents are created, how to triage them, and where to audit every delivery attempt.

Send Diffmon events to your systems with at-least-once delivery, HMAC signatures, secret rotation, retries, and redelivery.

How DiffMon protects fetches, secrets, and customer data across the platform.

How the worker schedules monitors, handles retries, and coordinates locks.

How we announce, schedule, and enforce breaking changes across the platform and API.

Track who changed members, tokens, and webhooks with request IDs for every action.

Org roles determine access to monitors, billing, webhooks, and member management.

How DiffMon versions the API, SDK, and worker behaviors to keep clients stable.

Use the public API to manage monitors, snapshots, and webhooks programmatically.

Create, scope, rotate, and revoke API tokens for programmatic access.

Use the TypeScript SDK to call DiffMon APIs with typed responses and retries.