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 /api/parcel-record. Share of records with each field:

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

Infrastructure in and around Travis County

Example requests for Travis 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 6801 RIVER PLACE BLVD, AUSTIN, TX 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=6801 RIVER PLACE BLVD, AUSTIN, TX' \
  https://api.korzy.co/api/search

import os
import requests

response = requests.get(
    "https://api.korzy.co/api/search",
    params={"q": "6801 RIVER PLACE BLVD, AUSTIN, TX"},
    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"])

{
  "results": [
    {
      "korzy_id": "48453-59c591cac9c31e33ed3e",
      "address": "6801 RIVER PLACE BLVD",
      "city": "AUSTIN",
      "postcode": "78726",
      "county": "TRAVIS",
      "statefp": "48",
      "longitude": -97.84150879055349,
      "latitude": 30.396027852696697,
      "match_type": "exact",
      "parcelid": "0151370601",
      "parceladdr": "6801 RIVER PLACE BLVD",
      "parcelcity": "AUSTIN",
      "situs_zip": "78726",
      "taxacres": 107.2117,
      "totalvalue": 0,
      "land_value_usd": 16740560,
      "improvement_value_usd": 112543219,
      "market_value_usd": 129283779,
      "updated": "2026-01-01",
      "geoid": "48453"
    }
  ],
  "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, 48453-59c591cac9c31e33ed3e, in records. 1 credit per 10 records requested.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-97.841509' \
  --data-urlencode 'latitude=30.396028' \
  --data-urlencode 'limit=5' \
  https://api.korzy.co/api/query/point

const params = new URLSearchParams({"longitude": "-97.841509", "latitude": "30.396028", "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 nearby data-center projects

/api/datacenters/context lists data-center projects within 10 km of the point, nearest first. 1 credit per 10 records requested.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-97.841509' \
  --data-urlencode 'latitude=30.396028' \
  --data-urlencode 'radius_km=10' \
  --data-urlencode 'limit=3' \
  https://api.korzy.co/api/datacenters/context

import os
import requests

response = requests.get(
    "https://api.korzy.co/api/datacenters/context",
    params={"longitude": "-97.841509", "latitude": "30.396028", "radius_km": "10", "limit": "3"},
    headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
    timeout=30,
)
response.raise_for_status()
for project in response.json()["projects"]:
    print(project["name"], project["status"], project["distance_km"])

{
  "projects": [],
  "radius_km": 10,
  "limit": 3,
  "truncated": false
}

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. 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 Travis County?

Korzy tracks about 15 data-center projects in Travis County: 10 status not reported, 5 operating and 1 under construction. /api/datacenters/context lists projects within 10 km of any 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%. /api/utilities/context returns the water and sewer matches at a 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