Durham County, NC parcel and infrastructure data API

Korzy has about 130,000 parcel records for Durham County, North Carolina, with source updates through June 2026. Nearly every record carries owner names, values, land use and building size; 51% include last sale. In and around the county the API also maps 6 data-center projects (3 operating); 5 power plants with about 20 MW of capacity, led by solar; and about 50 miles of active rail. Look up any parcel by address or coordinates, then check nearby data-center projects, utilities and grid context at the same point.

Parcel coverage in Durham County

About 130,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from June 2026. Each record has a stable korzy_id you can store and look up again with /v1/records/{id}. Share of records with each field:

FieldCoverageShare
Situs addressNearly all · 100%
Owner nameNearly all · 99%
Assessed or market valueNearly all · 99%
Year builtNot published
Building sizeNearly all · 100%
Last saleMany · 51%
Land useNearly all · 100%
ZoningNot published

Owner name and mailing address are returned by /v1/enrich with the owner group, at 2 credits per parcel instead of 1 credit. 99% of Durham County records carry an owner name.

Infrastructure in and around Durham County

Power plants

5 operable plants with about 20 MW of nameplate capacity; largest by capacity: solar, other fuels.

Within 50 km: /v1/lookup section power; details: /v1/records/{id}

Substations and transmission

About 65 in-service substations, 9 rated 230 kV or higher.

About 310 miles of transmission lines: about 140 mi at 100–161 kV; about 120 mi at 220–287 kV; about 10 mi at 500 kV.

Water and sewer service

Service areas of about 25 community water systems cover about 55% of the county.

Sewer service areas of 6 systems cover about 56%.

At an address or point: /v1/lookup section utilities

Data-center projects

6 tracked projects: 3 operating, 3 status not reported. Reported operating capacity: about 55 MW.

Within 10 km: /v1/lookup section datacenters

Flood zones and wetlands

Special flood hazard areas cover about 15% of the county on the current federal flood maps, published October 2026.

Mapped wetlands cover about 7%.

At an address or point: /v1/lookup section environment

Rail, ports and freight

  • About 50 miles of active rail, about 35 of it main line
  • About 25 miles of national freight network highway

Within 25 km: /v1/lookup section logistics

Example requests for Durham County

The lookup response is a real production response, trimmed to the main fields. Every request needs an API key with api:read; see authentication and credits and limits.

1. Find a parcel and nearby data-center projects

/v1/lookup matches 600 E UMSTEAD ST, DURHAM, NC and returns the parcel's korzy_id and record, plus the data-center projects within 10 km, nearest first. 2 credits.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"address":"600 E UMSTEAD ST, DURHAM, NC","sections":["datacenters"]}' \
  https://api.korzy.co/v1/lookup
Python
import os
import requests

response = requests.post(
    "https://api.korzy.co/v1/lookup",
    json={"address": "600 E UMSTEAD ST, DURHAM, NC", "sections": ["datacenters"]},
    headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
    timeout=60,
)
response.raise_for_status()
body = response.json()
parcel = body["parcels"]["records"][0]
print(parcel["korzy_id"], body["sections"]["datacenters"]["status"])
Production response (trimmed)
{
  "location": {
    "longitude": -78.89636415648647,
    "latitude": 35.98189765,
    "address": "600 E UMSTEAD ST, DURHAM",
    "match_type": "exact"
  },
  "parcels": {
    "records": [
      {
        "id": "37063-88571cb68715446fb91d",
        "korzy_id": "37063-88571cb68715446fb91d",
        "parcelid": "0831026315",
        "parceladdr": "600 E UMSTEAD ST",
        "parcelcity": "DURHAM",
        "situs_zip": "27701",
        "statefp": "37",
        "geoid": "37063",
        "longitude": -78.89636415648647,
        "latitude": 35.98189765,
        "usedesc": "CMNTY SVC/ SCHOOL",
        "land_use_code": "RU-5(2)",
        "bldgsqft": 57057,
        "building_count": 0,
        "taxacres": 5.92,
        "totalvalue": 4636244,
        "land_value_usd": 702792,
        "improvement_value_usd": 3933452,
        "saledate": "2017-04-05",
        "updated": "2026-05-13"
      }
    ],
    "truncated": false
  },
  "sections": {
    "datacenters": {
      "status": "ok",
      "data": {
        "radius_km": 10,
        "projects": [
          {
            "id": "datacenter:dc_6c9847efb0e719cbf347",
            "project_id": "dc_6c9847efb0e719cbf347",
            "name": "Brandaleone Lab for Data and Visualization",
            "operator": "Duke Libraries",
            "status": "unknown",
            "state": "NC",
            "longitude": -78.9385323,
            "latitude": 36.0030993,
            "location_precision": "exact",
            "source_count": 2,
            "source_date": "2026-02-09",
            "mapped": true,
            "distance_km": 4.466593184745539
          },
          {
            "id": "datacenter:dc_3489db0891e335efd2d4",
            "project_id": "dc_3489db0891e335efd2d4",
            "name": "CyrusOne Raleigh-Durham I (DUR1)",
            "operator": "CyrusOne",
            "status": "operating",
            "state": "NC",
            "city": "Durham",
            "address": "2223 Northeast Creek Parkway",
            "longitude": -78.8810471,
            "latitude": 35.9353037,
            "location_precision": "exact",
            "operational_mw": 50,
            "source_count": 1,
            "source_date": "2026-09-24",
            "mapped": true,
            "distance_km": 5.361301703709993
          },
          {
            "id": "datacenter:dc_7ba300efc3ab343a998b",
            "project_id": "dc_7ba300efc3ab343a998b",
            "name": "TierPoint Raleigh - RTP",
            "operator": "TierPoint",
            "status": "operating",
            "state": "NC",
            "city": "Durham",
            "address": "99 T.W. Alexander Drive",
            "longitude": -78.852029,
            "latitude": 35.9248595,
            "location_precision": "approximate",
            "source_count": 1,
            "source_date": "2026-09-24",
            "mapped": true,
            "distance_km": 7.493407399217366
          }
        ],
        "truncated": false,
        "note": "Straight-line distance to the reported project point; inspect location_precision. Projects merge supported source matches, not every nearby building. Approximate locations do not identify a parcel. Reported IT load, facility power, planned capacity and estimates remain separate source claims. No record or unknown status does not establish absence or inactivity."
      },
      "provenance": [
        {
          "dataset": "datacenters",
          "as_of": "2026-11-02",
          "data_version": "20261102T123021962884Z"
        }
      ]
    }
  },
  "credits": {
    "charged": 2,
    "refunded": 0
  }
}

2. Add owner and sale fields

/v1/enrich returns the fields you choose for up to 25 parcels per request; here the parcel 37063-88571cb68715446fb91d, with the owner group. 2 credits.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"items":[{"korzy_id":"37063-88571cb68715446fb91d"}],"fields":["identity","sale","owner"]}' \
  https://api.korzy.co/v1/enrich

3. Fetch the record again by ID

/v1/records/{id} returns the stored parcel's full record, without owner fields. 1 credit.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  https://api.korzy.co/v1/records/37063-88571cb68715446fb91d
JavaScript
const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("37063-88571cb68715446fb91d")}`, {
  headers: { Authorization: `Bearer ${process.env.KORZY_API_KEY}` },
});
if (!response.ok) throw new Error(`Korzy API ${response.status}`);
const { record } = await response.json();
console.log(record.parceladdr, record.usedesc);

Durham County data questions

How many parcels in Durham County include building size?
About 130,000 of about 130,000 parcel records (100%) include building size.
Does the Korzy API return owner names for Durham County parcels?
Yes. 99% of Durham County parcel records carry an owner name. Ask /v1/enrich for the owner group; each parcel then costs 2 credits instead of 1 credit. Lookups and records never include owner fields.
How many data-center projects are in Durham County?
Korzy tracks 6 data-center projects in Durham County: 3 operating and 3 status not reported. A /v1/lookup with the datacenters section lists projects within 10 km of any address or point.
How much power generation is in Durham County?
5 operable power plants in Durham County total about 20 MW of nameplate capacity, mainly solar and other fuels.
Which water systems serve Durham County?
Service areas of about 25 community water systems cover about 55% of Durham County, and sewer service areas cover about 56%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.

More featured counties

All featured North Carolina counties

Build on Durham County parcel data

Lookups, enrichment and records work the same in every county Korzy covers. Credits are shared across parcels, utilities, environment, logistics, power, grid, data-center and terrain sections.