Parcel Data API - Boundaries, Owners, Zoning, Land Use

Turn an address, an assessor parcel number, an owner name, a coordinate or a map polygon into the full land parcel record: the boundary itself, who owns it, how it is zoned, what it is worth and what it last sold for.

This actor calls a parcel data API on your behalf and stores one row per parcel. Bring your own key: paste your account token into the input and the run uses your own plan and your own contract.

What you get

• Nine ways in. Street address, assessor parcel number, owner name, latitude and longitude, GeoJSON polygon, the provider's parcel path, its stable parcel id, a nationwide field search, and a cheap typeahead that ranks address suggestions.
• The boundary, not just the attributes. Every parcel row carries its GeoJSON geometry and a computed centroid, so the output drops straight into a map, a spatial join or a GIS.
• Ownership as recorded. Owner name plus the tax mailing address, which is what separates an owner occupier from an absentee landlord or a holding company.
• Zoning twice over. The county's own zoning code and description, plus the standardised zoning type that means the same thing across state lines.
• Land use twice over. The county use code and description, plus the Land Based Classification Standards activity code and its description.
• Value and sale history. Assessed total, land and improvement values, the value type behind them, and the last sale amount, sale date and ownership transfer date.
• Risk and context. FEMA flood zone and subtype, USPS vacancy and residential delivery flags, census tract, unified school district and qualified opportunity zone status.
• Structures. Building count, total footprint area, year built, number of stories and structure style, plus matched building footprint rows when your account carries that dataset.
• A nationwide field search. Filter every parcel in the country by owner name, state, county, postal code, zoning, standard land use, acreage, year built, sale price, sale date, land value, building count, vacancy or opportunity zone status.
• Every county column kept. The curated columns sit at the top level for sorting and filtering; the provider's whole field bag rides along in fields so nothing is thrown away.

Pay per result

You are charged per record, never per request, and only for rows that carry real data. An address the provider has no parcel for is stored with the reason and costs nothing.

Event	Price	What it covers
Parcel record returned	$0.012	One parcel with boundary, ownership, zoning, land use, assessment, sale history and risk context
Address suggestion returned	$0.002	One ranked typeahead suggestion with the parcel id, path, address and centroid

Matched building footprints are stored but never charged for, because the parcel they belong to already was.

Quick start

1. Generate an API token in the API section of your provider account profile.
2. Paste it into API token.
3. Pick a What this run does mode. Address mode with one address in Addresses is the fastest way to see a real row.
4. Set Maximum rows to the most you want to pay for.
5. Run it.

FAQ

What is a parcel data API?

A parcel data API returns the record a county assessor holds for one piece of land: its legal boundary, its assessor parcel number, its owner and their mailing address, its zoning and land use, its assessed value and its last recorded sale. This actor reads a nationwide parcel dataset assembled from those county records and standardised into one schema, so a parcel in Wayne County, Michigan and a parcel in Dallas County, Texas come back with the same column names.

How do I find a parcel when I only have an address?

Use address mode, and set Restrict to a state or county when the street name is common. If your addresses are messy, run typeahead mode first: it returns ranked suggestions with the provider's stable parcel id for a fifth of the price, and you then spend a full lookup only on the ids you keep.

What is an assessor parcel number?

An assessor parcel number, also written APN or PIN, is the identifier a county assessor assigns to a parcel for tax purposes. It is unique inside its county but not between counties, so parcel number mode also takes a county path to say which county you mean. Punctuation is ignored when matching, so 02001069-71 and 0200106971 find the same parcel.

Can I find every property one owner holds?

Yes. Owner mode searches by owner name and returns every parcel recorded to that name, which is how portfolio research, due diligence and skip tracing usually start. Names are matched from the beginning, so a last name or the start of a company name works and at least four characters are needed. Owner search covers the United States only.

Can I search a whole neighbourhood or flood zone?

Yes. Area mode takes a GeoJSON Feature Collection, Feature or bare geometry and returns every parcel inside it. Polygons, points, lines and their multi variants all work, a radius in metres buffers the shape, and the provider caps a single search area at 80 square miles.

How do I search the whole country by attribute?

Query mode filters the nationwide dataset by the fields the provider indexes for it: owner name, state, county, postal code, zoning code, standardised zoning type, land use activity, acreage, year built, sale price, sale date, land value, building count, postal vacancy and residential flags, and qualified opportunity zone status. The provider allows at most four distinct fields in one search. A minimum and a maximum on the same measure count as one field, not two, and this actor checks the count before the first request rather than letting the provider refuse it mid run.

Does this return the parcel boundary?

Yes. Every parcel row carries the GeoJSON polygon or multipolygon in geometry, plus a computed latitude and longitude centroid. Turn Include boundary geometry off when you only want attributes and want smaller rows.

What about buildings on the parcel?

When your account carries the matched building footprints dataset, footprint rows come back alongside the parcels they sit on, each carrying the footprint geometry and the parcel ids it overlaps. Every parcel row also carries the building count, total footprint square footage, year built, stories and structure style from the assessor record.

Which countries are covered?

The United States and Puerto Rico by default. Set Country to ca for Canada or to a European country code your plan covers. Coverage is enabled per account, so the provider rather than this actor decides which codes work. Owner search is United States only.

What happens if my key is missing or rejected?

The run ends cleanly with the reason as its status message rather than failing with a stack trace. A missing token, an empty input, a token the provider will not accept and an exhausted record allowance are all treated as answers, not faults.

Is my API key stored anywhere?

No. It is read from the run input or from the DATA_API_KEY environment secret, used for that run's requests, and never written to the dataset or the log. On a POST it travels in the request body rather than the URL, so it does not end up in a proxy log.

Example output

{
  "recordType": "address",
  "requested": "440 Burroughs St, Detroit, MI",
  "found": true,
  "parcelId": "83cf8982-b8f8-415e-8cba-f388978f7367",
  "parcelPath": "/us/mi/wayne/detroit/364491",
  "parcelNumber": "02001069-71",
  "address": "440 BURROUGHS ST",
  "city": "DETROIT",
  "county": "wayne",
  "state": "MI",
  "postalCode": "48202-3429",
  "fipsCode": "26163",
  "owner": "TECHONE DEVELOPMENT LLC",
  "ownerMailingAddress": "440 BURROUGHS, DETROIT, MI, 48202",
  "landUseCode": "22320",
  "landUseDescription": "OFFICE BLDG-3 STORIES OR MORE",
  "standardLandUse": "Office",
  "zoning": "SD2",
  "zoningDescription": "Special Development District Mixed Use",
  "zoningType": "Mixed",
  "acres": 0.66,
  "buildingCount": 1,
  "buildingSquareFeet": 28713,
  "yearBuilt": 1926,
  "stories": 5,
  "assessedValue": 0,
  "valueType": "ASSESSED",
  "saleAmount": 0,
  "lastTransferDate": "2019-07-31",
  "floodZone": "X",
  "floodZoneDescription": "AREA OF MINIMAL FLOOD HAZARD",
  "vacancy": "N",
  "schoolDistrict": "Detroit Public Schools Community District",
  "latitude": 42.3650758,
  "longitude": -83.0730601,
  "geometry": { "type": "Polygon", "coordinates": [] }
}

Keyword map

parcel data API, property boundary API, land parcel API, assessor parcel number lookup, APN lookup API, property owner search API, parcel ownership data, GIS parcel boundaries, GeoJSON parcel API, zoning data API, land use data API, property assessment data, county assessor data API, reverse geocoding to parcel, property records by address, owner portfolio search, vacant land search, opportunity zone parcels, flood zone by parcel, building footprint data, real estate data API, land data for site selection