Clayton County, GA parcel and infrastructure data API

Korzy has about 91,000 parcel records for Clayton County, Georgia, with source updates through October 2026. Nearly every record carries owner names, values, last sale and land use; 92% include year built and 88% include building size. In and around the county the API also maps 1 data-center project; and about 40 miles of active rail. Look up any parcel by address or coordinates, then check water, sewer and infrastructure context at the same point.

Parcel coverage in Clayton County

About 91,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:

FieldCoverageShare
Situs addressNearly all · 100%
Owner nameNearly all · 99%
Assessed or market valueNearly all · 99%
Year builtMost · 92%
Building sizeMost · 88%
Last saleNearly all · 99%
Land useNearly all · 99%
ZoningNearly all · 99%

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. 99% of Clayton County records carry an owner name.

Infrastructure in and around Clayton County

Substations and transmission

About 35 in-service substations, 6 rated 230 kV or higher.

About 180 miles of transmission lines: about 95 mi at 100–161 kV; about 65 mi at 220–287 kV; about 20 mi at 500 kV.

Water and sewer service

Service areas of 8 community water systems cover about 99% of the county.

Sewer service areas of 8 systems cover about 81%.

At a point: /api/utilities/context

Data-center projects

1 tracked project: 1 permitted. Reported planned capacity: about 1,400 MW.

Within 10 km of a point: /api/datacenters/context

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 active rail, about 25 of it main line
  • About 30 miles of national freight network highway

Within 25 km of a point: /api/logistics/context

Example requests for Clayton County

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 28 VALLEY HILL RD, RIVERDALE, GA 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=28 VALLEY HILL RD, RIVERDALE, GA' \
  https://api.korzy.co/api/search
Python
import os
import requests

response = requests.get(
    "https://api.korzy.co/api/search",
    params={"q": "28 VALLEY HILL RD, RIVERDALE, GA"},
    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": "13063-862357640e60755eae19",
      "address": "28 VALLEY HILL RD",
      "city": "RIVERDALE",
      "postcode": "30274",
      "county": "Clayton",
      "statefp": "13",
      "longitude": -84.38951473072359,
      "latitude": 33.55886515,
      "match_type": "exact",
      "parcelid": "13173C A003",
      "parceladdr": "28 VALLEY HILL RD",
      "parcelcity": "RIVERDALE",
      "situs_zip": "30274",
      "usedesc": "Religious (Church, Synagogue, Mosque)",
      "land_use_code": "620",
      "zoning_code": "RS110",
      "yearbuilt": 1969,
      "bldgsqft": 2536,
      "taxacres": 1.41,
      "totalvalue": 188200,
      "land_value_usd": 30300,
      "improvement_value_usd": 157900,
      "assessed_value_usd": -75280,
      "market_value_usd": 188200,
      "saledate": "2019-08-10",
      "saleamt": 0,
      "updated": "2026-10-30",
      "geoid": "13063"
    }
  ],
  "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, 13063-862357640e60755eae19, in records. 1 credit per 10 records requested.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-84.389515' \
  --data-urlencode 'latitude=33.558865' \
  --data-urlencode 'limit=5' \
  https://api.korzy.co/api/query/point
JavaScript
const params = new URLSearchParams({"longitude": "-84.389515", "latitude": "33.558865", "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=-84.389515' \
  --data-urlencode 'latitude=33.558865' \
  https://api.korzy.co/api/utilities/context
Python
import os
import requests

response = requests.get(
    "https://api.korzy.co/api/utilities/context",
    params={"longitude": "-84.389515", "latitude": "33.558865"},
    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": -84.389515,
  "latitude": 33.558865,
  "matches": {
    "water": [
      {
        "feature_id": "water:40918",
        "name": "CLAYTON COUNTY WATER AUTHORITY",
        "boundary_basis": "System Sourced"
      }
    ],
    "sewer": [
      {
        "feature_id": "sewer:5609",
        "name": "E L Huie-Casey Natural Treatment System",
        "boundary_basis": "Modeled"
      }
    ]
  },
  "nearby_treatment": [
    {
      "feature_id": "treatment:15087",
      "name": "E L Huie-Casey Natural Treatment System",
      "distance_km": 11.426180380498284
    },
    {
      "feature_id": "treatment:3119",
      "name": "Northeast Clayton WRF",
      "distance_km": 11.852474725227292
    }
  ]
}

Clayton County data questions

How many parcels in Clayton County include year built?
About 84,000 of about 91,000 parcel records (92%) include year built.
Does the Korzy API return owner names for Clayton County parcels?
Yes. 99% of Clayton County 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 Clayton County?
Korzy tracks 1 data-center project in Clayton County: 1 permitted. /api/datacenters/context lists projects within 10 km of any point.
Which water systems serve Clayton County?
Service areas of 8 community water systems cover about 99% of Clayton County, and sewer service areas cover about 81%. /api/utilities/context returns the water and sewer matches at a point.
How much of Clayton County is in a mapped flood zone?
About 9% of Clayton County's area falls within special flood hazard areas on the current federal flood maps, and mapped wetlands cover about 4%.

More featured counties

All featured Georgia counties

Build on Clayton County 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.