Capitol Planning Region, CT parcel and infrastructure data API

Parcel coverage in Capitol Planning Region

About 360,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from October 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:

Owner name and mailing address are returned with include_owner=true, which doubles a request's cost: a parcel record costs 2 credits instead of 1. 45% of Capitol Planning Region records carry an owner name.

Infrastructure in and around Capitol Planning Region

Example requests for Capitol 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 20 FRONT ST, Hartford, 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=20 FRONT ST, Hartford, CT' \
  https://api.korzy.co/api/search

import os
import requests

response = requests.get(
    "https://api.korzy.co/api/search",
    params={"q": "20 FRONT ST, Hartford, 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"])

{
  "results": [
    {
      "korzy_id": "09110-0e0d5291c0ed7807eb52",
      "address": "20 FRONT ST",
      "city": "Hartford",
      "postcode": "06103",
      "county": "Capitol",
      "statefp": "09",
      "longitude": -72.67130763374782,
      "latitude": 41.763158649999994,
      "match_type": "exact",
      "parcelid": "269360017",
      "parceladdr": "20 FRONT ST",
      "parcelcity": "Hartford",
      "situs_zip": "06103",
      "usedesc": "ST-CRDA EXEMPT",
      "land_use_code": "909.0",
      "zoning_code": "DT-1",
      "yearbuilt": 2014,
      "bldgsqft": 118955,
      "taxacres": 0,
      "totalvalue": 6512909,
      "land_value_usd": 0,
      "improvement_value_usd": 17722200,
      "assessed_value_usd": 6512909,
      "saledate": "2012-07-30",
      "saleamt": 0,
      "updated": "2021-01-01",
      "geoid": "09110"
    }
  ],
  "truncated": false
}

With include_owner=true (2 credits) the record adds owner fields, shown here as placeholders:

{
  "owner_name": "EXAMPLE HOLDINGS LLC",
  "owner_mailing_address": "100 EXAMPLE ST, SAMPLE CITY, ST 00000"
}

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, 09110-0e0d5291c0ed7807eb52, in records. 1 credit per 10 records requested.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-72.671308' \
  --data-urlencode 'latitude=41.763159' \
  --data-urlencode 'limit=5' \
  https://api.korzy.co/api/query/point

const params = new URLSearchParams({"longitude": "-72.671308", "latitude": "41.763159", "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=-72.671308' \
  --data-urlencode 'latitude=41.763159' \
  https://api.korzy.co/api/utilities/context

import os
import requests

response = requests.get(
    "https://api.korzy.co/api/utilities/context",
    params={"longitude": "-72.671308", "latitude": "41.763159"},
    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"]])

{
  "longitude": -72.671308,
  "latitude": 41.763159,
  "matches": {
    "water": [
      {
        "feature_id": "water:35297",
        "name": "METROPOLITAN DISTRICT COMMISSION",
        "boundary_basis": "System Sourced"
      }
    ],
    "sewer": [
      {
        "feature_id": "sewer:151",
        "name": "HARTFORD WPCF",
        "boundary_basis": "Sourced"
      }
    ]
  },
  "nearby_treatment": [
    {
      "feature_id": "treatment:624",
      "name": "EAST HARTFORD WPCF",
      "distance_km": 1.7189798345662248
    },
    {
      "feature_id": "treatment:622",
      "name": "HARTFORD WPCF",
      "distance_km": 3.7408304222037594
    }
  ]
}

Capitol Planning Region data questions

How many parcels in Capitol Planning Region include year built?

About 330,000 of about 360,000 parcel records (92%) include year built.

Does the Korzy API return owner names for Capitol Planning Region parcels?

Yes. 45% of Capitol Planning Region parcel records carry an owner name. Add include_owner=true to a point, search or parcel-record request; it doubles the request's cost, so a single parcel record costs 2 credits.

How many data-center projects are in Capitol Planning Region?

Korzy tracks 4 data-center projects in Capitol Planning Region: 2 proposed, 1 operating and 1 status not reported. /api/datacenters/context lists projects within 10 km of any point.

How much power generation is in Capitol Planning Region?

About 50 operable power plants in Capitol Planning Region total about 390 MW of nameplate capacity, mainly solar, natural gas and battery and pumped storage.

Which water systems serve Capitol Planning Region?

Service areas of about 120 community water systems cover about 38% of Capitol Planning Region, and sewer service areas cover about 26%. /api/utilities/context returns the water and sewer matches at a point.

More featured counties

• Naugatuck Valley Planning Region, CTBorders Capitol Planning Region · about 170,000 parcels
• South Central Connecticut Planning Region, CTBorders Capitol Planning Region · about 190,000 parcels
• Southeastern Connecticut Planning Region, CTBorders Capitol Planning Region · about 120,000 parcels
• Hampden County, MABorders Capitol Planning Region · about 160,000 parcels
• Western Connecticut Planning Region, CTabout 180,000 parcels
• Greater Bridgeport Planning Region, CTabout 100,000 parcels

All featured Connecticut counties