Greater Bridgeport Planning Region, CT parcel and infrastructure data API

Parcel coverage in Greater Bridgeport Planning Region

About 100,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. 59% of Greater Bridgeport Planning Region records carry an owner name.

Infrastructure in and around Greater Bridgeport Planning Region

Example requests for Greater Bridgeport 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 425 THORME ST, Bridgeport, 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=425 THORME ST, Bridgeport, CT' \
  https://api.korzy.co/api/search

import os
import requests

response = requests.get(
    "https://api.korzy.co/api/search",
    params={"q": "425 THORME ST, Bridgeport, 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": "09120-e3719b4635391051ae47",
      "address": "425 THORME ST",
      "city": "Bridgeport",
      "postcode": "06606",
      "county": "Greater Bridgeport",
      "statefp": "09",
      "longitude": -73.21383720368078,
      "latitude": 41.20523475,
      "match_type": "exact",
      "parcelid": "22784",
      "parceladdr": "425 THORME ST",
      "parcelcity": "Bridgeport",
      "situs_zip": "06606",
      "usedesc": "Public School Mdl 94",
      "land_use_code": "934",
      "zoning_code": "P2",
      "yearbuilt": 1964,
      "bldgsqft": 124670,
      "taxacres": 11,
      "totalvalue": 24350130,
      "land_value_usd": 4396490,
      "improvement_value_usd": 30213870,
      "assessed_value_usd": 24350130,
      "saledate": "2000-01-01",
      "saleamt": 0,
      "updated": "2025-01-01",
      "geoid": "09120"
    }
  ],
  "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, 09120-e3719b4635391051ae47, in records. 1 credit per 10 records requested.

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

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

import os
import requests

response = requests.get(
    "https://api.korzy.co/api/utilities/context",
    params={"longitude": "-73.213837", "latitude": "41.205235"},
    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": -73.213837,
  "latitude": 41.205235,
  "matches": {
    "water": [
      {
        "feature_id": "water:34943",
        "name": "AQUARION-EASTERN FAIRFIELD COUNTY",
        "boundary_basis": "System Sourced"
      }
    ],
    "sewer": [
      {
        "feature_id": "sewer:129",
        "name": "BRIDGEPORT EAST SIDE",
        "boundary_basis": "Sourced"
      }
    ]
  },
  "nearby_treatment": [
    {
      "feature_id": "treatment:674",
      "name": "TRUMBULL SEWER SYSTEM",
      "distance_km": 4.636264590924442
    },
    {
      "feature_id": "treatment:599",
      "name": "BRIDGEPORT WESTSIDE",
      "distance_km": 4.9532656947841565
    }
  ]
}

Greater Bridgeport Planning Region data questions

How many parcels in Greater Bridgeport Planning Region include year built?

About 91,000 of about 100,000 parcel records (91%) include year built.

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

Yes. 59% of Greater Bridgeport 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 Greater Bridgeport Planning Region?

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

How much power generation is in Greater Bridgeport Planning Region?

9 operable power plants in Greater Bridgeport Planning Region total about 1,200 MW of nameplate capacity, mainly natural gas, battery and pumped storage and other fuels.

Which water systems serve Greater Bridgeport Planning Region?

Service areas of 4 community water systems cover about 64% of Greater Bridgeport Planning Region, and sewer service areas cover about 34%. /api/utilities/context returns the water and sewer matches at a point.

More featured counties

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

All featured Connecticut counties