Western Connecticut Planning Region, CT parcel and infrastructure data API
Korzy has about 180,000 parcel records for Western Connecticut Planning Region, Connecticut, with source updates through August 2026. Nearly every record carries values; 92% include last sale and 91% include year built. In and around the county the API also maps 3 data-center projects (2 operating); 1 port with reported cargo; and about 10 power plants with about 280 MW of capacity, led by oil. Look up any parcel by address or coordinates, then check water, sewer and infrastructure context at the same point.
Parcel coverage in Western Connecticut Planning Region
About 180,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from August 2026. Each record has a stable korzy_id you can store and look up again with /api/parcel-record. Share of records with each field:
| Field | Coverage | Share |
|---|---|---|
| Situs address | Nearly all · 99% | |
| Owner name | Not published | |
| Assessed or market value | Nearly all · 95% | |
| Year built | Most · 91% | |
| Building size | Most · 82% | |
| Last sale | Most · 92% | |
| Land use | Most · 84% | |
| Zoning | Not published |
Western Connecticut Planning Region records do not include owner names. See pricing for credit costs.
Infrastructure in and around Western Connecticut Planning Region
Power plants
About 10 operable plants with about 280 MW of nameplate capacity; largest by capacity: oil, natural gas, battery and pumped storage.
Plant details: /api/power/plants/{plant_id}
Substations and transmission
About 60 in-service substations, 2 rated 230 kV or higher.
About 190 miles of transmission lines: about 160 mi at 100–161 kV; about 30 mi at 345 kV.
Water and sewer service
Service areas of about 80 community water systems cover about 33% of the county.
Sewer service areas of about 15 systems cover about 14%.
At a point: /api/utilities/context
Data-center projects
3 tracked projects: 2 operating, 1 status not reported.
Within 10 km of a point: /api/datacenters/context
Grid capacity data
7 utility-published grid capacity layers cover parts of Western Connecticut Planning Region, including load headroom, substation and feeder ratings.
Sources and dates: /api/grid/capacity/summary
Flood zones and wetlands
Special flood hazard areas cover about 9% of the county on the current federal flood maps, published September 2026.
Mapped wetlands cover about 4%.
Rail, ports and freight
- About 40 miles of national freight network highway
- 1 port area with reported cargo tonnage
Within 25 km of a point: /api/logistics/context
Example requests for Western Connecticut Planning Region
Real responses from the production API, trimmed to the main fields. Every request needs an API key with api:read; see authentication and credits and limits.
1. Find a parcel by address
/api/search matches 15 HUBBARD RD, NORWALK, CT and returns the parcel's korzy_id, coordinates and record. 1 credit.
curl --fail-with-body -sS --get \
-H "Authorization: Bearer $KORZY_API_KEY" \
--data-urlencode 'q=15 HUBBARD RD, NORWALK, CT' \
https://api.korzy.co/api/searchPython
import os
import requests
response = requests.get(
"https://api.korzy.co/api/search",
params={"q": "15 HUBBARD RD, NORWALK, CT"},
headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
timeout=30,
)
response.raise_for_status()
parcel = response.json()["results"][0]
print(parcel["korzy_id"], parcel["longitude"], parcel["latitude"])Response (trimmed)
{
"results": [
{
"korzy_id": "09190-9150e307593ce602fa63",
"address": "15 HUBBARD RD",
"city": "NORWALK",
"postcode": "06897",
"county": "Western Connecticut",
"statefp": "09",
"longitude": -73.43381883794257,
"latitude": 41.19282345028376,
"match_type": "exact",
"parcelid": "7c4e0167-409e-48df-940e-274289b8bfcd",
"parceladdr": "15 HUBBARD RD",
"parcelcity": "NORWALK",
"situs_zip": "06897",
"usedesc": "Commercial",
"yearbuilt": 1986,
"bldgsqft": 11309,
"totalvalue": 2565710,
"saledate": "1984-01-13",
"saleamt": 0,
"updated": "2026-08-06",
"geoid": "09190"
}
],
"truncated": false
}2. Look up the parcel at a point
/api/query/point returns every parcel whose boundary covers the coordinates; here it returns the same record, 09190-9150e307593ce602fa63, in records. 1 credit per 10 records requested.
curl --fail-with-body -sS --get \
-H "Authorization: Bearer $KORZY_API_KEY" \
--data-urlencode 'longitude=-73.433819' \
--data-urlencode 'latitude=41.192823' \
--data-urlencode 'limit=5' \
https://api.korzy.co/api/query/pointJavaScript
const params = new URLSearchParams({"longitude": "-73.433819", "latitude": "41.192823", "limit": "5"});
const response = await fetch(`https://api.korzy.co/api/query/point?${params}`, {
headers: { Authorization: `Bearer ${process.env.KORZY_API_KEY}` },
});
if (!response.ok) throw new Error(`Korzy API ${response.status}`);
const { records } = await response.json();
console.log(records.map((record) => record.korzy_id));3. Check water and sewer service
/api/utilities/context returns the water and sewer service areas at the point and the nearest treatment plants. 1 credit.
curl --fail-with-body -sS --get \
-H "Authorization: Bearer $KORZY_API_KEY" \
--data-urlencode 'longitude=-73.433819' \
--data-urlencode 'latitude=41.192823' \
https://api.korzy.co/api/utilities/contextPython
import os
import requests
response = requests.get(
"https://api.korzy.co/api/utilities/context",
params={"longitude": "-73.433819", "latitude": "41.192823"},
headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
timeout=30,
)
response.raise_for_status()
matches = response.json()["matches"]
print([area["name"] for area in matches["water"]])Response (trimmed)
{
"longitude": -73.433819,
"latitude": 41.192823,
"matches": {
"water": [
{
"feature_id": "water:34943",
"name": "AQUARION-EASTERN FAIRFIELD COUNTY",
"boundary_basis": "System Sourced"
}
],
"sewer": [
{
"feature_id": "sewer:173",
"name": "NORWALK WPCF",
"boundary_basis": "Sourced"
}
]
},
"nearby_treatment": [
{
"feature_id": "treatment:636",
"name": "NEW CANAAN WPCF",
"distance_km": 7.1508253669139314
},
{
"feature_id": "treatment:653",
"name": "REDDING - GEORGETOWN WPCF",
"distance_km": 7.280333292475896
}
]
}Western Connecticut Planning Region data questions
- How many parcels in Western Connecticut Planning Region include year built?
- About 160,000 of about 180,000 parcel records (91%) include year built.
- Does the Korzy API return owner names for Western Connecticut Planning Region parcels?
- Western Connecticut Planning Region parcel records do not include owner names. Values, land use and building facts are returned where the county publishes them.
- How many data-center projects are in Western Connecticut Planning Region?
- Korzy tracks 3 data-center projects in Western Connecticut Planning Region: 2 operating and 1 status not reported. /api/datacenters/context lists projects within 10 km of any point.
- How much power generation is in Western Connecticut Planning Region?
- About 10 operable power plants in Western Connecticut Planning Region total about 280 MW of nameplate capacity, mainly oil, natural gas and battery and pumped storage.
- Which water systems serve Western Connecticut Planning Region?
- Service areas of about 80 community water systems cover about 33% of Western Connecticut Planning Region, and sewer service areas cover about 14%. /api/utilities/context returns the water and sewer matches at a point.
More featured counties
- Greater Bridgeport Planning Region, CTBorders Western Connecticut Planning Region · about 100,000 parcels
- Naugatuck Valley Planning Region, CTBorders Western Connecticut Planning Region · about 170,000 parcels
- Westchester County, NYBorders Western Connecticut Planning Region · about 250,000 parcels
- Capitol Planning Region, CTabout 360,000 parcels
- South Central Connecticut Planning Region, CTabout 190,000 parcels
- Southeastern Connecticut Planning Region, CTabout 120,000 parcels
Build on Western Connecticut Planning Region parcel data
Search, point and record lookups work the same in every county Korzy covers. Credits are shared across parcels, utilities, environment, logistics and data-center routes.