Added
- Added an optional
addressable_onlyquery parameter to GET /v1/search/suggest. It defaults tofalse, so existing consumers keep the full address universe, and it applies to both the autocomplete and the postcode-only address routes. - Some background on why this matters. UK addresses have a lifecycle. Each address is a Local Property Identifier (LPI) that carries a logical status, because real-world addresses change over time: a house is renumbered, a large plot is split into flats, two units are merged, or a building is demolished and rebuilt under a new address. The address data keeps the old entries rather than deleting them, so that historical references still resolve, and marks each one as approved (the current, live address) or historical and superseded (an address that existed once but no longer does).
- A plain autocomplete returns that whole universe, so two records on the same street and postcode can both match a query even though only one is a property a buyer can transact on today. The superseded record looks like a real address but no longer points at a live property.
- With
addressable_only=true, suggestions are restricted to addresses whose LPI is currently approved, so every result is a live, addressable property and the historical and superseded entries are dropped. Use it for address pickers in checkout, quoting or onboarding flows, where each suggestion has to resolve to a real property, and leave it off for broad search that should still match older or renamed addresses.