Address Standardization for Voter Rolls & Census

Census enumeration and voter registration both depend on assigning each resident to the correct small-area geography — a district, precinct, or block — based on their address.

The problem

Self-reported addresses on registration forms vary widely in format, and small inconsistencies (an abbreviated street type, a missing district) can lead to a resident being assigned to the wrong precinct or excluded from an automated match entirely.

How address standardisation helps

Standardising each submitted address into structured components and canonical expansions standardizes raw voter registration inputs against official electoral roll datasets. Expanded thoroughfare variations ("Street" vs "St") and explicit county/district fields (suburb / stateDistrict) eliminate fuzzy-matching errors and ensure accurate precinct and enumeration block assignment.

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": "77 Elm Street, Cook County, Chicago IL 60601" }'

200 OK

{
  "houseNumber": "77",
  "road": "elm street",
  "postcode": "60601",
  "suburb": "cook county",
  "city": "chicago",
  "state": "il",
  "country": "USA",
  "expansions": [
    "77 elm street cook county chicago il 60601 usa",
    "77 elm street cook county chicago illinois 60601 usa"
  ]
}

Key response fields

Field	Why it matters here
expansions	Standardized canonical strings used to match voter roll records against district master files without manual intervention.
suburb / stateDistrict	Captures county, borough, or ward context when present — often the primary key for precinct mapping.
city / postcode	Narrows the match to the correct enumeration or voting district.
houseNumber / road	Required for precise block-level assignment where district boundaries split a street.