For developers who depend on other people's APIs
Hear about a vendor's breaking change before your integration does
Watch the changelogs and deprecation pages of the services you integrate with, and get a webhook when their text changes.
The problem
Payment providers, shipping APIs and identity platforms announce breaking changes on a changelog page and in an email to whoever signed up three years ago. The first your team hears of it is the integration failing on the date the notice gave.
How domscout handles it
A monitor on each changelog or deprecation page compares the page's rendered text on every run, not its raw HTML, so a rebuild of the vendor's docs site is not a change and a new entry is. The webhook names the run and the two captures, and both are saved, so you can show exactly what was added. Route each monitor's webhook to the team that owns that integration.
Where it shows up
- A changelog watch for every external API a service calls.
- Deprecation pages for the SDKs and runtimes you build on.
- Terms and pricing pages of the platforms you build on top of.
The request
POST /monitors. Monitors start at Pro: 10 monitors, checked as often as every 60 minutes. Business allows 100 every 15 minutes and Enterprise 500 every 5. Each run is billed as a capture; creating and managing a monitor is free.
Go further
More in Monitoring and alerts: Website change monitoring · A feed for a site without RSS · Competitor price tracking · Minimum advertised price checks · New job posting alerts · Tender, grant and notice alerts · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.