How to Search for Properties

To search Shovels Properties, use the Search Properties endpoint. Each result is one property with its permit history already summarized on the record—permit counts, work-type tags, latest activity dates, contractors, and job values—so you don’t have to stitch individual permits together yourself.

Properties are currently in beta. Query parameters, response fields, and the absence-trust surface may still change in response to how the endpoint is used in practice.

Required Parameters

Every search needs a scope: a location or an owner (or both).

Parameter	Description
`geo_id`	A 2-letter state code, 5-digit ZIP, ZIP+4, or a Shovels geolocation ID for a state, county, city, or address
`legal_owner`	A property owner name, matched on its canonical form. Pass up to 10 `legal_owner` parameters. Without a `geo_id`, this searches the owner’s properties nationwide

Omitting both returns a 422 error. Jurisdiction geo_ids are not accepted—see Properties vs Permits for why.

curl -X GET \
  "https://api.shovels.ai/v2/properties/search?geo_id=94103&permit_tags=solar" \
  -H "X-API-Key: YOUR_API_KEY_HERE"

To turn a typed address into a geo_id, call Search Addresses first. See Resolving addresses.

Permit Filters

Filter	Description
`permit_tags`	Canonical tags, one key per tag (`?permit_tags=roofing&permit_tags=-solar`). A positive tag keeps properties with that work type on some permit; a `-` prefix (e.g. `-solar`) keeps properties with no permit of that type on record—see Absence search. Several positive tags require every tag, but not all on the same permit—matching is at address grain, a deliberate divergence from Search Permits
`permit_status`	Statuses, one key per status (`?permit_status=final&permit_status=active`): `final`, `in_review`, `inactive`, `active`. On its own it keeps properties with a permit in any of the named statuses; combined with positive tags, the tag and status must appear on the same permit. `unknown` is not filterable
`permit_from`	ISO date (`YYYY-MM-DD`). Positive filters match since this date; a pure-absence exclusion means “none since this date”
`permit_tags_unfinaled`	Keeps properties with an unfinaled permit of each named tag, one key per tag—see Unfinaled permits

These three filters take repeated keys, not one comma-joined value. permit_tags=solar,-roofing is rejected with a 422 naming the bad token—send permit_tags=solar&permit_tags=-roofing instead.An unrecognized tag is also a 422 rather than an empty result, so a typo fails loudly here. Search Permits returns 200 with zero items for the same typo, which is easy to misread as “no such properties.”

permit_to (and any other upper date bound) is not supported on properties. The property record keeps only the latest permit date per work type, so a closed date window can’t be answered correctly. Use Search Permits for date-window queries.

With multiple positive tags, each tag must be present on the property but they may come from different permits. This differs from /permits/search, where multiple tags must appear on the same permit.

Filter	Description
`property_type`	Repeatable: `residential`, `commercial`, `industrial`, `agricultural`, `vacant land`, `exempt`, `miscellaneous`, `office`, `recreational`
`property_min_market_value` / `property_max_market_value`	Assessed market value range in cents (dollars × 100)
`property_min_lot_size` / `property_max_lot_size`	Lot size range in square feet
`property_min_building_area` / `property_max_building_area`	Building area range in square feet
`property_min_unit_count` / `property_max_unit_count`	Unit count range
`property_min_year_built` / `property_max_year_built`	Year built range

Attribute data (value, size, year, units, type) is available for roughly 60–70% of properties. A property with no value for an attribute never matches a range filter on it, so attribute filters narrow results to the covered set.

Pagination

Results are sorted most recently permitted first.

size — results per page (1–100, default 10)
cursor — pass the next_cursor from the previous response to fetch the next page
include_total_count — set to true on the first page (no cursor) to include total_count. The count is exact up to 10,000; above that it is reported as a “greater than or equal to” value.

Knowledge Base

Required Parameters

Permit Filters

Property Attribute Filters

​Required Parameters

​Permit Filters

​Property Attribute Filters

​Pagination

​Related Articles

Required Parameters

Permit Filters

Property Attribute Filters

Pagination

Related Articles