Bexar County, TX parcel and infrastructure data API

Korzy has about 710,000 parcel records for Bexar County, Texas, with source updates through February 2026. Nearly every record carries owner names, values, land use and building size; 86% include year built and 84% include last sale. In and around the county the API also maps about 35 data-center projects (7 operating and 2 under construction); about 20 power plants with about 4,500 MW of capacity, led by natural gas; and about 260 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 Bexar County

About 710,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from February 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 · 98%
Assessed or market valueNearly all · 98%
Year builtMost · 86%
Building sizeNearly all · 98%
Last saleMost · 84%
Land useNearly all · 98%
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. 98% of Bexar County records carry an owner name.

Infrastructure in and around Bexar County

Power plants

About 20 operable plants with about 4,500 MW of nameplate capacity; largest by capacity: natural gas, coal, battery and pumped storage. Proposed generators add about 1,200 MW.

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

Substations and transmission

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

About 1,000 miles of transmission lines: about 770 mi at 100–161 kV; about 240 mi at 345 kV.

Water and sewer service

Service areas of about 60 community water systems cover about 92% of the county.

Sewer service areas of about 15 systems cover about 69%.

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

Data-center projects

About 35 tracked projects: 7 operating, 2 under construction, 25 status not reported. Reported operating capacity: about 190 MW. Reported planned capacity: about 180 MW.

Within 10 km: /v1/lookup section datacenters

Flood zones and wetlands

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

Mapped wetlands cover about 1%.

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

Rail, ports and freight

  • About 260 miles of active rail, about 150 of it main line
  • About 160 miles of national freight network highway
  • 1 intermodal rail terminal

Within 25 km: /v1/lookup section logistics

Example requests for Bexar 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 9999 WESTOVER HILLS BLVD, SAN ANTONIO, TX 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":"9999 WESTOVER HILLS BLVD, SAN ANTONIO, TX","sections":["datacenters"]}' \
  https://api.korzy.co/v1/lookup
Python
import os
import requests

response = requests.post(
    "https://api.korzy.co/v1/lookup",
    json={"address": "9999 WESTOVER HILLS BLVD, SAN ANTONIO, TX", "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": -98.68825642707266,
    "latitude": 29.466433569050935,
    "address": "9999 WESTOVER HILLS BLVD, SAN ANTONIO",
    "match_type": "exact"
  },
  "parcels": {
    "records": [
      {
        "id": "48029-7d6f1e4a0c88dece493c",
        "korzy_id": "48029-7d6f1e4a0c88dece493c",
        "parcelid": "17642-008-0010",
        "parceladdr": "9999 WESTOVER HILLS BLVD",
        "parcelcity": "SAN ANTONIO",
        "situs_zip": "78251",
        "statefp": "48",
        "geoid": "48029",
        "longitude": -98.68825642707266,
        "latitude": 29.466433569050935,
        "land_use_code": "313",
        "yearbuilt": 1996,
        "taxacres": 0,
        "land_value_usd": 0,
        "improvement_value_usd": 0,
        "market_value_usd": 40000000,
        "saledate": "2022-03-16",
        "updated": "2026-01-01"
      }
    ],
    "truncated": false
  },
  "sections": {
    "datacenters": {
      "status": "ok",
      "data": {
        "radius_km": 10,
        "projects": [
          {
            "id": "datacenter:dc_383627757ff4e7223c39",
            "project_id": "dc_383627757ff4e7223c39",
            "name": "CyrusOne SAT1 (San Antonio)",
            "operator": "CyrusOne",
            "status": "operating",
            "state": "TX",
            "city": "San Antonio",
            "address": "9999 Westover Hills Boulevard",
            "longitude": -98.68823995424793,
            "latitude": 29.46641075,
            "location_precision": "footprint",
            "source_count": 3,
            "source_date": "2026-07-23",
            "mapped": true,
            "distance_km": 0.002996910888561835
          },
          {
            "id": "datacenter:dc_143b89424362a9a82ee2",
            "project_id": "dc_143b89424362a9a82ee2",
            "name": "Unnamed data center",
            "operator": "Frost Bank",
            "status": "unknown",
            "state": "TX",
            "longitude": -98.68756881713054,
            "latitude": 29.47008515,
            "location_precision": "footprint",
            "source_count": 2,
            "source_date": "2026-05-29T16:10:13Z",
            "mapped": true,
            "distance_km": 0.41145828672851137
          },
          {
            "id": "datacenter:dc_4d6947285c88b1683c83",
            "project_id": "dc_4d6947285c88b1683c83",
            "name": "Unnamed data center",
            "operator": "CHRISTUS Health",
            "status": "unknown",
            "state": "TX",
            "longitude": -98.68634842417035,
            "latitude": 29.47025415,
            "location_precision": "footprint",
            "source_count": 2,
            "source_date": "2026-05-29T16:10:13Z",
            "mapped": true,
            "distance_km": 0.4632485194595477
          }
        ],
        "truncated": true,
        "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 48029-7d6f1e4a0c88dece493c, 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":"48029-7d6f1e4a0c88dece493c"}],"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/48029-7d6f1e4a0c88dece493c
JavaScript
const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("48029-7d6f1e4a0c88dece493c")}`, {
  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);

Bexar County data questions

How many parcels in Bexar County include year built?
About 610,000 of about 710,000 parcel records (86%) include year built.
Does the Korzy API return owner names for Bexar County parcels?
Yes. 98% of Bexar 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 Bexar County?
Korzy tracks about 35 data-center projects in Bexar County: 25 status not reported, 7 operating 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 Bexar County?
About 20 operable power plants in Bexar County total about 4,500 MW of nameplate capacity, mainly natural gas, coal and battery and pumped storage.
Which water systems serve Bexar County?
Service areas of about 60 community water systems cover about 92% of Bexar County, and sewer service areas cover about 69%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.

More featured counties

All featured Texas counties

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