Vepler logo
v2.156.0

Filter properties by recent price reductions, with stricter query validation

The property query, aggregate and tiles endpoints gain two price-reduction filters, and aggregate now returns a 400 when a query names a field it does not support.

Added

  • Added the boolean filter fields marketStatus.hasPriceReductionSale and marketStatus.hasPriceReductionRent, usable in the query body of POST /v1/property/query, POST /v1/property/aggregate and GET /v1/property/tiles/{z}/{x}/{y}. They filter to properties whose sale or rental price has been reduced, and support the eq, ne, in and nin comparators.
  • The new fields sit alongside the existing market-status filters, so a price-reduction condition can be combined with other conditions in the same query group, and used identically across query, aggregate and tile requests.

Changed

  • On POST /v1/property/aggregate, naming a filter field that is not recognised now returns 400 with error code validation_error and a message of the form Unsupported field: <field>, so a mistyped field in an aggregation is reported as a client error you can correct.

Affected endpoints