Address Standardization for Real Estate Listings

The same property is often listed simultaneously across an MLS feed, a brokerage site, and third-party portals — each with its own address formatting.

The problem

Without a reliable way to tell that "4500 Park Ave #12" and "4500 Park Avenue, Unit 12" are the same unit, listing aggregators show duplicate entries, and property-history tools fail to link past sales to the same address.

How address standardisation helps

Standardising each listing’s address into canonical components and fully expanded strings (expansions) provides a consistent, robust join key across feeds. Abbreviations like "Ave" vs "Avenue" and unit formats like "#12" vs "Unit 12" resolve to identical canonical strings, letting you merge duplicate listings and link historical records reliably.

Example

POST /v1/address/normalize

curl -X POST "https://api.goodvat.com/v1/address/normalize" \
  -H "Authorization: Bearer $GOODVAT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "query": "4500 Park Avenue, Unit 12, Dallas TX 75205" }'

200 OK

{
  "houseNumber": "4500",
  "road": "park avenue",
  "unit": "unit 12",
  "postcode": "75205",
  "city": "dallas",
  "state": "tx",
  "country": "USA",
  "expansions": [
    "4500 park avenue unit 12 dallas tx 75205 usa",
    "4500 park avenue unit 12 dallas texas 75205 usa"
  ]
}

Key response fields

Field	Why it matters here
expansions	Standardized canonical strings used as primary match keys across MLS feeds and listing portals.
houseNumber / road / unit	Granular unit key for matching multi-family and condo properties.
postcode	Pre-filter for candidate matches before exact comparison.
city / state	Required for standard listing display and geographic search indexing.