Vepler logo
v5.19.0

Market status and time on market follow each advert's own lifecycle

Market status, time on market and lettings price history are built from each advert's own status history, so an agreed sale keeps its price detail.

Changed

  • A property whose sale or let is agreed but still being marketed keeps its market history. marketStatus.forSale reads sstc or under_offer while the advert stands, and priceChangeSale and priceChangeRent go on carrying every asking price recorded for the property, so an agreed sale still shows the asking prices and the derived detail behind it.
  • marketStatus is worked out from each advert's own status history rather than from the date the advert record carries. Where a source republishes an advert, or restates the date it says the advert was published, the property's market status follows the sequence of states that advert actually passed through. Read marketStatus.timeline for that sequence.
  • lastOTM, backOTM, lastOTMRent and backOTMRent count the current marketing spell rather than the whole life of the advert record. lastOTM gives the start of the current period on the sale market, and backOTM is true when the property came back to that market within 180 days of an earlier period ending. A property advertised, withdrawn, then advertised again reads as a new spell.
  • Lettings price history records a change of rent, not a change of quoting period. When an advert republishes a rent per calendar month where it was previously quoted per week, the API keeps the rent it already holds and writes no entry to priceHistory, so a let's price history describes what is being asked rather than how the figure was expressed. This applies to every advert ingested or refreshed from this release.
  • The property fields above are held per property, so each property picks the behaviour up as it is next re-aggregated. One with an advert still on the market refreshes continuously; one with no recent advert activity keeps its existing record until something touches it.