Vepler logo
v5.8.0

Structured address lines on property responses, and a portal pricing page

Property responses break the address into line_1, line_2, line_3 and post_town, those lines are filterable in property query, and the portal shows per-line-item pricing with your effective rate.

Added

  • Property responses now include a structured address breakdown: address.line_1 (organisation, sub-building, building and street), address.line_2 (locality), address.line_3 and address.post_town, on GET /v1/property/{locationIds}, POST /v1/property/query and every other property-returning endpoint. The lines sit inside the default address projection at the core tier, are composed by the same canonical builder as GET /v1/address/postcodes/{postcode} (so the two surfaces break a UPRN down identically), and appear together or not at all; displayAddress is always populated.
  • The address lines are filterable in POST /v1/property/query: address.line_1, address.line_2, address.post_town (alias town), address.country, address.countryCode and address.eircode take exact-match term comparators, sort and aggregate, and are listed in GET /v1/property/attributes. Street names live inside address.line_1.
  • The developer portal gains a pricing page (Dashboard, then Pricing): per-line-item credit rates grouped by product, your tenant-effective rate beside the list price with any licence or agreement override marked, and licence-gated products flagged for contact. The page is rendered by the same engine that rates real requests, so it cannot drift from what you are charged, and it notes the monthly charge-once rule: an item charged this calendar month repeats free.

Affected endpoints