Canadian County, OK parcel and infrastructure data API
Korzy has about 82,000 parcel records for Canadian County, Oklahoma, with source updates through October 2026. Nearly every record carries owner names, values, last sale and land use; 78% include year built and 78% include building size. In and around the county the API also maps 2 data-center projects; 4 power plants with about 900 MW of capacity, led by natural gas; and about 85 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 Canadian County
About 82,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 /v1/records/{id}. Share of records with each field:
| Field | Coverage | Share |
|---|---|---|
| Situs address | Most · 92% | |
| Owner name | Nearly all · 99% | |
| Assessed or market value | Nearly all · 100% | |
| Year built | Most · 78% | |
| Building size | Most · 78% | |
| Last sale | Nearly all · 96% | |
| Land use | Nearly all · 99% | |
| Zoning | Not 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 Canadian County records carry an owner name.
Infrastructure in and around Canadian County
Power plants
4 operable plants with about 900 MW of nameplate capacity; largest by capacity: natural gas, wind, oil.
Within 50 km: /v1/lookup section power; details: /v1/records/{id}
Substations and transmission
About 30 in-service substations, 2 rated 230 kV or higher.
About 360 miles of transmission lines: about 90 mi at under 100 kV; about 170 mi at 100–161 kV; about 95 mi at 345 kV.
Water and sewer service
Service areas of about 20 community water systems cover about 56% of the county.
Sewer service areas of about 10 systems cover about 8%.
At an address or point: /v1/lookup section utilities
Data-center projects
2 tracked projects: 2 proposed. Reported planned capacity: about 2,500 MW.
Within 10 km: /v1/lookup section datacenters
Flood zones and wetlands
Special flood hazard areas cover about 19% of the county on the current federal flood maps, published September 2026.
Mapped wetlands cover about 2%.
At an address or point: /v1/lookup section environment
Rail, ports and freight
- About 85 miles of active rail, about 75 of it main line
- About 35 miles of national freight network highway
Within 25 km: /v1/lookup section logistics
Example requests for Canadian 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 its water and sewer service
/v1/lookup matches 1201 HEALTH CENTER PKWY, YUKON, OK and returns the parcel's korzy_id and record, plus the water and sewer service areas at the parcel and the nearest treatment plants. 2 credits.
curl --fail-with-body -sS \
-H "Authorization: Bearer $KORZY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"address":"1201 HEALTH CENTER PKWY, YUKON, OK","sections":["utilities"]}' \
https://api.korzy.co/v1/lookupPython
import os
import requests
response = requests.post(
"https://api.korzy.co/v1/lookup",
json={"address": "1201 HEALTH CENTER PKWY, YUKON, OK", "sections": ["utilities"]},
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"]["utilities"]["status"])Production response (trimmed)
{
"location": {
"longitude": -97.76342567315479,
"latitude": 35.486515281867526,
"address": "1201 HEALTH CENTER PARKWAY EAST, YUKON",
"match_type": "exact"
},
"parcels": {
"records": [
{
"id": "40017-4ecfaef9ae82060c4297",
"korzy_id": "40017-4ecfaef9ae82060c4297",
"parcelid": "090125546",
"parceladdr": "1201 HEALTH CENTER PARKWAY EAST",
"parcelcity": "YUKON",
"situs_zip": "73099",
"statefp": "40",
"geoid": "40017",
"longitude": -97.76342567315479,
"latitude": 35.486515281867526,
"land_use_code": "UC",
"taxacres": 5,
"totalvalue": 1089000,
"land_value_usd": 1089000,
"assessed_value_usd": 130680,
"saledate": "2013-09-23",
"saleamt": 1089000,
"updated": "2026-10-30"
}
],
"truncated": false
},
"sections": {
"utilities": {
"status": "ok",
"data": {
"water": [
{
"id": "utility:water:38950",
"feature_id": "water:38950",
"name": "YUKON",
"boundary_basis": "System Sourced"
}
],
"sewer": [
{
"id": "utility:sewer:13141",
"feature_id": "sewer:13141",
"name": "YUKON STP",
"boundary_basis": "Modeled"
}
],
"treatment_plants": [
{
"id": "utility:treatment:8967",
"feature_id": "treatment:8967",
"name": "YUKON STP",
"distance_km": 5.195726158273555
},
{
"id": "utility:treatment:13449",
"feature_id": "treatment:13449",
"name": "PIEDMONT WWT",
"distance_km": 16.06892301149308
},
{
"id": "utility:treatment:8966",
"feature_id": "treatment:8966",
"name": "MUSTANG WWT",
"distance_km": 18.14332673543049
}
],
"truncated": {
"water": false,
"sewer": false
}
},
"provenance": [
{
"dataset": "water",
"data_version": "63b7c1c3-9661-4fed-a59f-ddbfff80c2e4"
},
{
"dataset": "sewer",
"data_version": "63b7c1c3-9661-4fed-a59f-ddbfff80c2e4"
},
{
"dataset": "treatment",
"data_version": "63b7c1c3-9661-4fed-a59f-ddbfff80c2e4"
}
]
}
},
"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 40017-4ecfaef9ae82060c4297, 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":"40017-4ecfaef9ae82060c4297"}],"fields":["identity","sale","owner"]}' \
https://api.korzy.co/v1/enrich3. 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/40017-4ecfaef9ae82060c4297JavaScript
const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("40017-4ecfaef9ae82060c4297")}`, {
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);Canadian County data questions
- How many parcels in Canadian County include year built?
- About 64,000 of about 82,000 parcel records (78%) include year built.
- Does the Korzy API return owner names for Canadian County parcels?
- Yes. 99% of Canadian 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 Canadian County?
- Korzy tracks 2 data-center projects in Canadian County: 2 proposed. A /v1/lookup with the datacenters section lists projects within 10 km of any address or point.
- How much power generation is in Canadian County?
- 4 operable power plants in Canadian County total about 900 MW of nameplate capacity, mainly natural gas, wind and oil.
- Which water systems serve Canadian County?
- Service areas of about 20 community water systems cover about 56% of Canadian County, and sewer service areas cover about 8%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.
More featured counties
- Oklahoma County, OKBorders Canadian County · about 320,000 parcels
- Tulsa County, OKabout 330,000 parcels
- Rogers County, OKabout 49,000 parcels
Build on Canadian 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.