Travis County, TX parcel and infrastructure data API

Parcel coverage in Travis County

About 420,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from August 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:

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

Infrastructure in and around Travis County

Example requests for Travis 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 6801 RIVER PLACE BLVD, AUSTIN, 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":"6801 RIVER PLACE BLVD, AUSTIN, TX","sections":["datacenters"]}' \
  https://api.korzy.co/v1/lookup

import os
import requests

response = requests.post(
    "https://api.korzy.co/v1/lookup",
    json={"address": "6801 RIVER PLACE BLVD, AUSTIN, 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"])

{
  "location": {
    "longitude": -97.84150879055349,
    "latitude": 30.396027852696697,
    "address": "6801 RIVER PLACE BLVD, AUSTIN",
    "match_type": "exact"
  },
  "parcels": {
    "records": [
      {
        "id": "48453-59c591cac9c31e33ed3e",
        "korzy_id": "48453-59c591cac9c31e33ed3e",
        "parcelid": "0151370601",
        "parceladdr": "6801 RIVER PLACE BLVD",
        "parcelcity": "AUSTIN",
        "situs_zip": "78726",
        "statefp": "48",
        "geoid": "48453",
        "longitude": -97.84150879055349,
        "latitude": 30.396027852696697,
        "taxacres": 107.2117,
        "totalvalue": 0,
        "land_value_usd": 16740560,
        "improvement_value_usd": 112543219,
        "market_value_usd": 129283779,
        "updated": "2026-01-01"
      }
    ],
    "truncated": false
  },
  "sections": {
    "datacenters": {
      "status": "ok",
      "data": {
        "radius_km": 10,
        "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 48453-59c591cac9c31e33ed3e, 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":"48453-59c591cac9c31e33ed3e"}],"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/48453-59c591cac9c31e33ed3e

const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("48453-59c591cac9c31e33ed3e")}`, {
  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);

Travis County data questions

How many parcels in Travis County include year built?

About 42,000 of about 420,000 parcel records (10%) include year built.

Does the Korzy API return owner names for Travis County parcels?

Yes. 88% of Travis 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 Travis County?

Korzy tracks about 15 data-center projects in Travis County: 10 status not reported, 5 operating and 1 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 Travis County?

About 20 operable power plants in Travis County total about 1,600 MW of nameplate capacity, mainly natural gas, battery and pumped storage and solar.

Which water systems serve Travis County?

Service areas of about 100 community water systems cover about 66% of Travis 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

• Bexar County, TXabout 710,000 parcels
• Dallas County, TXabout 840,000 parcels
• Harris County, TXabout 1.6 million parcels
• Tarrant County, TXabout 750,000 parcels
• Denton County, TXabout 380,000 parcels

All featured Texas counties