Monitor
Save the places behind your customers' records and we watch them. When a value moves past your threshold after a refresh, a signed webhook tells you, with the value before and after, the periods compared, and whether the area moved or our method did.
See it run
A portfolio is saved, a refresh lands, one place crosses the threshold, and a signed event arrives with its cause and both of its dates.
You set what counts. We compare each place with its previous period, hold back thin data, and send every material change with its cause and both of its dates.
You set the threshold. Each place is compared with its previous period, or with the first one you saved, and only moves past the threshold are reported.
Every change carries the value before and after, the periods compared, and its cause: the area moved, our method changed, or both.
The period the data describes and the moment our store recorded it, so you can tell a late publisher from a recent move.
A price move built on too few sales is held until there is enough behind it, by a sample-size gate you set.
watch · compare · signed webhooks
Map up to 1,000 records to places in one call, or 20,000 as a job, and save them as a portfolio. Then read the portfolio's change report whenever you need it, or let the feed come to you.
After each refresh that recorded a change, a webhook signed with HMAC-SHA256 arrives at your endpoint, with the change, its cause and the methodology versions before and after. Verify the signature and act.
Save the places that matter, set what counts, and get a signed, explained heads-up when one moves.
Get a sandbox key
The Monitor workspace in the console
A watch on the places behind a customer's portfolio, a listing inventory or a whole dataset, on your own thresholds.
The changes that matter reach your systems already checked and explained.
Watch the places behind one customer's holdings and show them what changed since they last looked.
Keep the places behind a listing inventory under watch and refresh what each listing says when a value moves.
Run a change report over a whole dataset between two refreshes and ship only the rows that moved.
Decide the percentage that counts as a move and the number of sales a price move needs, per report.
Frequently asked
Any places in Great Britain you save into a portfolio: sale prices, crime, school ratings and the rest of the signals. Save a handful, or map 1,000 records in one call and 20,000 as a job.
You set a percentage threshold, choose whether to compare with the previous period or the first one saved, and set how many sales a price move needs before it counts.
A price move built on only a handful of sales is not reliable, so it is held back until there are enough sales behind it to trust.
As a signed webhook to your own endpoint after the refresh that recorded the change. Webhooks only: your systems receive the event and route it. Each one carries the value before and after, the period, the recorded date and the cause.
Whether the area moved, our method changed between the two values, or both. A method change lists the releases behind it and the methodology versions before and after, so you never mistake a method change for a move in the place.
After every data refresh: a monthly full refresh, a weekly incremental one and a daily check for new crime data. Or on demand, whenever you pull a change report.
Save a portfolio of places and subscribe a webhook endpoint, or book a call and we set it up on your own records.
Save the places, set what counts, and receive signed, explained changes. Start in the free sandbox.