Get an API key

Tulsa County, OK parcel and infrastructure data API

Korzy has about 330,000 parcel records for Tulsa County, Oklahoma, with source updates through October 2026. Nearly every record carries values; 90% include last sale and 84% include year built. In and around the county the API also maps about 25 data-center projects (15 operating and 2 under construction); 5 power plants with about 2,500 MW of capacity, led by natural gas; and 1 port with reported cargo. Look up any parcel by address or coordinates, then check nearby data-center projects, utilities and grid context at the same point.

Get an API keyRead the API docs

Parcel coverage in Tulsa County

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

FieldCoverageShare
Situs addressNearly all · 99%
Owner nameSome · 16%
Assessed or market valueNearly all · 97%
Year builtMost · 84%
Building sizeMost · 84%
Last saleMost · 90%
Land useSome · 16%
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. 16% of Tulsa County records carry an owner name.

Infrastructure in and around Tulsa County

Power plants

5 operable plants with about 2,500 MW of nameplate capacity; largest by capacity: natural gas, battery and pumped storage, hydro.

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

Substations and transmission

About 140 in-service substations, 5 rated 230 kV or higher.

About 620 miles of transmission lines: about 90 mi at under 100 kV; about 440 mi at 100–161 kV; about 80 mi at 345 kV.

Water and sewer service

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

Sewer service areas of about 20 systems cover about 56%.

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

Data-center projects

About 25 tracked projects: 15 operating, 2 under construction, 7 status not reported. Reported planned capacity: about 45 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 170 miles of active rail, about 85 of it main line
  • About 40 miles of national freight network highway
  • 1 port area with reported cargo tonnage

Within 25 km: /v1/lookup section logistics

Example requests for Tulsa 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 5681 S MINGO RD E, TULSA, OK 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":"5681 S MINGO RD E, TULSA, OK","sections":["datacenters"]}' \
  https://api.korzy.co/v1/lookup
Python
import os
import requests

response = requests.post(
    "https://api.korzy.co/v1/lookup",
    json={"address": "5681 S MINGO RD E, TULSA, OK", "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": -95.8677657429566,
    "latitude": 36.0807844,
    "address": "5681 S MINGO RD E, TULSA",
    "match_type": "exact"
  },
  "parcels": {
    "records": [
      {
        "id": "40143-3846e039c51c2b63e422",
        "korzy_id": "40143-3846e039c51c2b63e422",
        "parcelid": "77520943152000",
        "parceladdr": "5681 S MINGO RD E",
        "parcelcity": "TULSA",
        "situs_zip": "741460000",
        "statefp": "40",
        "geoid": "40143",
        "longitude": -95.8677657429566,
        "latitude": 36.0807844,
        "usedesc": "Storage Warehouse",
        "land_use_code": "Commercial",
        "yearbuilt": 1977,
        "bldgsqft": 23950,
        "taxacres": 2.1117,
        "totalvalue": 1100000,
        "land_value_usd": 414000,
        "improvement_value_usd": 686000,
        "saledate": "2013-02-19",
        "saleamt": 275000,
        "updated": "2026-10-30"
      }
    ],
    "truncated": false
  },
  "sections": {
    "datacenters": {
      "status": "ok",
      "data": {
        "radius_km": 10,
        "projects": [
          {
            "id": "datacenter:dc_751bf63fdb78e313e40a",
            "project_id": "dc_751bf63fdb78e313e40a",
            "name": "Unnamed data center",
            "status": "unknown",
            "state": "OK",
            "longitude": -95.85414917495449,
            "latitude": 36.0812514,
            "location_precision": "footprint",
            "source_count": 2,
            "source_date": "2026-02-09",
            "mapped": true,
            "distance_km": 1.2247705529162964
          },
          {
            "id": "datacenter:dc_d30cd2e2e445f8febbe6",
            "project_id": "dc_d30cd2e2e445f8febbe6",
            "name": "TulsaConnect DC3",
            "status": "unknown",
            "state": "OK",
            "longitude": -95.8382826,
            "latitude": 36.0994735,
            "location_precision": "exact",
            "source_count": 2,
            "source_date": "2026-02-09",
            "mapped": true,
            "distance_km": 3.3670571264973677
          },
          {
            "id": "datacenter:dc_e6f52f4a1a2effd52121",
            "project_id": "dc_e6f52f4a1a2effd52121",
            "name": "Meta Project Anthem — Tulsa",
            "operator": "Meta",
            "status": "under_construction",
            "state": "OK",
            "city": "Tulsa",
            "address": "Near East 11th Street & 193rd East Avenue (Fair Oaks industrial park, East Tulsa)",
            "longitude": -95.88,
            "latitude": 36.14,
            "location_precision": "exact",
            "source_count": 1,
            "source_date": "2026-08-06",
            "mapped": true,
            "distance_km": 6.675574872599367
          }
        ],
        "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 40143-3846e039c51c2b63e422, 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":"40143-3846e039c51c2b63e422"}],"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/40143-3846e039c51c2b63e422
JavaScript
const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("40143-3846e039c51c2b63e422")}`, {
  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);

Tulsa County data questions

How many parcels in Tulsa County include year built?
About 280,000 of about 330,000 parcel records (84%) include year built.
Does the Korzy API return owner names for Tulsa County parcels?
Yes. 16% of Tulsa 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 Tulsa County?
Korzy tracks about 25 data-center projects in Tulsa County: 15 operating, 7 status not reported and 2 under construction. A /v1/lookup with the datacenters section lists projects within 10 km of any address or point.
How much power generation is in Tulsa County?
5 operable power plants in Tulsa County total about 2,500 MW of nameplate capacity, mainly natural gas, battery and pumped storage and hydro.
Which water systems serve Tulsa County?
Service areas of about 25 community water systems cover about 87% of Tulsa 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 Oklahoma counties

Build on Tulsa 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.

Get an API keySee pricingAPI referenceUse cases for parcel and infrastructure data