Parcel API

One request, the parcel behind it.

Resolve a point, a radius or any polygon to the parcels it touches, across 161.8M parcels in 52 states — one schema everywhere, so you write the query once.

See the plans API docs

From $29/mo · free sample without an account · no call

GET /v1/parcels/point

{
  "parcel_id": "0234170108",
  "owner_name": "AUSTIN RETAIL HOLDINGS LLC",
  "derived_owner_type": "LLC",
  "property_address_line1": "1100 CONGRESS AVE",
  "property_address_city": "AUSTIN",
  "assessed_value": 1284300,
  "acreage": 0.41,
  "land_use": "COMMERCIAL",
  "unified_land_use_category": "commercial",
  "zoning": "CBD",
  "year_built": 1974,
  "building_count": 1,
  "building_footprint_total_sqft": 14820,
  "geometry": { "type": "Polygon", "coordinates": [ … ] }
}

Endpoints

Three ways to ask

GET/v1/parcels/point1 credit

The parcel containing an exact latitude and longitude. The lookup behind an address, a rooftop or a dropped pin.

curl 'https://api.getparceldata.com/v1/parcels/point?lat=30.2672&lng=-97.7431' \
  -H 'Authorization: Bearer YOUR_KEY'

GET/v1/parcels/radius3 credits

Every parcel within N metres of a point. Comparables, neighbour notification lists, catchment analysis.

curl 'https://api.getparceldata.com/v1/parcels/radius?lat=30.2672&lng=-97.7431&radius=500' \
  -H 'Authorization: Bearer YOUR_KEY'

GET/v1/parcels/polygon3 credits

Every parcel intersecting an arbitrary WKT polygon — a service territory, a flood zone, a school district, a drawn AOI.

curl 'https://api.getparceldata.com/v1/parcels/polygon?wkt=POLYGON((...))' \
  -H 'Authorization: Bearer YOUR_KEY'

What comes back

One schema, every county

Identity

Parcel and address

parcel_id plus up to three alternates, full property address, and centroid coordinates.

Ownership

Owner and entity type

owner_name with mailing address, and derived_owner_type — LLC, LP, corporation, trust, REIT, government — so corporate holdings separate from individual ones without string matching.

Valuation

Assessor values

assessed, land and improvement values with the assessment year they came from.

Use

Land use and zoning

Raw assessor codes alongside unified_land_use_category and unified_zoning_category, so one query means the same thing in every county.

Structure

Buildings and geometry

Year built, floor area, and derived building statistics — footprint area, height, coverage — joined from building footprints. Plus parcel area, perimeter and shape compactness.

Provenance

Source and vintage

Every county page publishes its own field fill rates and data vintage rather than averaging them into a single number.

Plans

Priced per lookup, not per seat

Subscribe with a card and the key arrives by email. One lookup is one parcel returned, and included lookups reset monthly.

Starter

$29/mo

1,000 lookups included

$0.029 per lookup, included or over

1,000 lookups a month

Most teams

Growth

$99/mo

5,000 lookups included

$0.020 per lookup, included or over

5,000 lookups a month

Scale

$299/mo

25,000 lookups included

$0.012 per lookup, included or over

25,000 lookups a month

Building an agent? There is an MCP server, and the endpoints above are documented in OpenAPI. Need the whole dataset instead of queries? Bulk extracts start at $49.

Coverage

What the API can answer for

161.8M
parcels with geometry: 3,164
counties: 52
states and territories: 158.0M
building footprints joined

Field availability varies by county because assessors vary. The coverage dashboard publishes per-county fill rates and vintage rather than hiding them behind an average.

Start with an area

Draw a box.
Download the parcels.

See the parcel count before you pay, and the file in your inbox after.

Draw an area See pricing