Property Characteristics API - Owner, Risk, Home Prices

Turn a US street address into a persistent property id, then read everything the record holds: land, structure, ownership, roof age, climate risk, and the market around it.

What this actor does

• Address to property id. Resolve a street address to the provider's persistent numeric property identifier, with the standardised address, parcel number, county FIPS, owner name and coordinates. That id is stable, so it is the right key to store against your own records.
• Full characteristics profile. Land use and category, lot size in acres and square feet, living and building area, bedrooms, bathrooms, stories, building count, construction type, exterior wall, roof type and cover, foundation, basement area, garage spaces, pool, and owner occupancy and absentee flags.
• Honest year built. The provider marks a year built that its model estimated rather than the county recorded. Every row says which it is, in a yearBuiltIsEstimated column, so an estimate never reads as a fact.
• Roof age and climate risk. Estimated roof age with its confidence rank, and multi-peril risk across flood, wildfire, hurricane, tornado, hail, wind, heat and drought, with the perils actually returned named on the row.
• Market trends. Listing activity, closed sales, rents, the home price index and its forecast, for a ZIP, county, metro or state, over a month range or at the latest reading.
• Pay per result. You are charged for rows that carry a real record. Resolving an address to an id is free, and addresses the provider matches nothing to are free.

Bring your own key

This actor signs in with your own client id and client secret. Paste them into the input, or set the secret as DATA_API_KEY. Nothing runs on anyone else's credentials, and a run without them ends cleanly with an explanation rather than failing. A run also checks up front whether your credentials may call the dataset you picked, and stops with the list of the ones they can, rather than spending anything to find out.

Example output

{
  "recordType": "property-characteristics",
  "requested": "3001 Hackberry Rd, Irving, TX 75063",
  "found": true,
  "propertyId": "123456789",
  "landUse": "Single Family Residence",
  "lotAcres": 0.19,
  "lotSquareFeet": 8276,
  "yearBuilt": 2012,
  "yearBuiltIsEstimated": false,
  "livingSquareFootage": 2450,
  "bedrooms": 4,
  "totalBathrooms": 3,
  "stories": 2,
  "buildingCount": 1,
  "constructionType": "Wood Frame",
  "roofType": "Gable",
  "roofCover": "Composition Shingle",
  "foundation": "Slab",
  "garageSpaces": 2,
  "ownerOccupied": true
}

FAQ

What is the property id and why does it matter?

It is the provider's persistent numeric identifier for a US parcel, assigned to every residential and commercial property. Unlike an address it does not change when a street is renamed or a unit is renumbered, and unlike a parcel number it is unique nationally rather than per county. Every property dataset in this actor is keyed on it, which is why an address is resolved to one first.

Do I have to give a property id, or can I use an address?

Either. Put full street addresses in the input and the actor resolves each one before reading the dataset you asked for. That resolving step uses the provider's own identity lookup and is not charged by this actor. Lines that are already numeric ids skip it entirely, which is faster and exact.

How do I know whether the year built is real?

Check the yearBuiltIsEstimated column. The provider flags a construction year that came from its own model rather than from a county record, and this actor surfaces that flag on every characteristics and roof age row. Treat an estimated year as a statistical estimate, not as a document.

What climate perils are covered?

Flood, wildfire, hurricane, tornado, hail, wind, heat and drought, with current scores and forward projections under different emissions scenarios and time horizons. Which perils come back depends on where the property is and what your agreement includes, so each row names the perils that were actually returned rather than showing empty columns for the rest.

Can I get market data for a whole metro?

Yes. Switch to one of the five market modes and set the area type to metro CBSA code, county FIPS, ZIP or state, then list the areas. One run can cover many areas at once. Add a from and to month to get a time series, or leave both empty for the latest reading. A range needs both ends, and the actor tells you rather than sending a half-filled one.

Does it cover commercial property?

Property characteristics covers both residential and commercial parcels. Climate risk, roof age and all five market datasets are US residential only, which is the provider's own scope.

What does it cost?

Pricing is pay per result: 0.016 USD per property identity or characteristics record, 0.012 USD per roof age or climate risk reading, and 0.008 USD per market reading, with Apify platform usage included. Rows the provider found nothing for are not charged. You also need your own agreement with the data provider, which bills separately and licenses each dataset separately.

Does the actor fail if my credentials are wrong?

No. Missing credentials, rejected credentials, a dataset that is not on your agreement, or an empty input all end the run cleanly with a message saying what to change. Only a real outage or a bug fails the run.

Keyword map

property characteristics API, property data API, US property records, address to property id, CLIP identifier, parcel level identifier, property ownership data, owner occupied flag, absentee owner data, building characteristics API, roof age data, roof condition estimate, climate risk API, multi-peril risk scores, flood wildfire hurricane hail risk, property insurance underwriting data, home price index API, HPI forecast, housing market trends by ZIP, rental market data API, days on market data, mortgage collateral data, MISMO property data

---

Note: this actor was built against the provider's published developer documentation. Its endpoints and tool names are transcribed from that documentation and have not been exercised against a live account, because no production credential exists for it.