US Building Permit Leads — Multi-City avatar

US Building Permit Leads — Multi-City

Pricing

$4.00 / 1,000 results

Go to Apify Store
US Building Permit Leads — Multi-City

US Building Permit Leads — Multi-City

Fresh, normalized building-permit leads across NYC, SF, Chicago, Austin & Seattle. Filter by city, date, cost, keyword, ZIP. One unified schema.

Pricing

$4.00 / 1,000 results

Rating

0.0

(0)

Developer

Alfredo Carranza

Alfredo Carranza

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Fresh, normalized building-permit leads from five major US cities in one unified schema. Filter by city, issue date, job cost, work-description keyword, and ZIP. Built for contractors, roofers, solar installers, materials suppliers, and lead-gen agencies who want a clean, current feed of who just pulled a permit — and for what.

Cities covered

CitySourceCost filterOwner nameContractor name
New York CityDOB NOW: Build – Approved Permits
San FranciscoDBI Building Permits
ChicagoBuilding Permits✅ (contact 1)
AustinIssued Construction Permits❌ (not published)
SeattleBuilt Environment Permits

All sources are official open-data (Socrata) APIs — no login, no CAPTCHA, no proxies. Data is refreshed by the cities themselves, so maintenance is minimal.

Input

FieldTypeDescription
citiesarrayWhich cities to pull (default: all five).
sincestringOnly permits issued on/after YYYY-MM-DD.
minCostintegerMinimum estimated job cost (USD).
keywordstringCase-insensitive substring on the work description (e.g. roof, solar, pool).
zipFilterarrayRestrict to specific 5-digit ZIPs.
maxResultsPerCityintegerCap per city (default 1000).

Output — normalized lead schema

city, permit_id, permit_type, work_description, status,
issue_date, applied_date, estimated_cost,
address, zip, latitude, longitude,
owner_name, contractor_name, contractor_phone, source_url

Known limitations (read before buying)

  • Field coverage varies by city (see table). Not every city publishes cost, owner, or contractor. Fields are null where the source doesn't provide them — never fabricated.
  • Austin has no job cost in its public dataset. If you set minCost, Austin leads are excluded (can't verify the threshold).
  • contractor_phone is not available in the current public datasets for any city; the field exists for schema stability and forward compatibility.
  • Date semantics = permit issued date. "Applied" date is included where available.
  • These are public records. The product's value is unification, filtering, freshness, and delivery — not exclusive data.

Pricing

Pay-per-event: one permit-lead event per delivered lead. Configure the price in the Apify Console → Publication → Monetization.

Local development

python3.11 -m venv .venv
./.venv/bin/pip install -r requirements.txt
# edit storage/key_value_stores/default/INPUT.json
APIFY_LOCAL_STORAGE_DIR=./storage ./.venv/bin/python -m src

Pure-stdlib fetch engine (src/engine.py, src/cities.py) is import-safe and testable without the SDK via test_local.py.

Roadmap

  • Fix contractor_phone sourcing where a secondary dataset exposes it.
  • Add cities weekly (LA needs an app token; Boston, Seattle county, Denver, Portland are candidates) — each new city widens the lead over single-city competitors.