US Building Permits Scraper - 10 Cities in One Schema

Pull building permits from 10 US city open-data portals into a single normalized dataset - built for construction lead generation and sales-territory monitoring.

What it does

This building permits scraper aggregates permit records from 10 official US city open-data portals and normalizes them into one clean schema, so you never have to reconcile a different field layout for every city. It pulls high-intent construction data - permit type, status, address, valuation, dates, and (where the city publishes it) contractor and applicant names - and lets you filter by city, project value, keyword, contractor, and date range. Use it as a lightweight US building permits API for construction lead generation, then export straight to CSV, JSON, or Excel from the Apify dataset.

The moat is the per-city field mapping: each source portal labels its columns differently, and this actor maps all of them into the same output fields so your CRM, spreadsheet, or pipeline sees consistent building permit data by city.

Who it's for

• Construction lead-gen teams sourcing new-project and renovation leads
• Contractors and subcontractors watching their service area for fresh permits
• Building-material suppliers and distributors timing outreach to project starts
• Roofers, solar installers, and HVAC sales teams chasing permit-triggered demand
• Real-estate and proptech teams enriching properties with permit activity
• Market researchers and analysts tracking construction volume by city

What you get / Output

Every record is normalized to the same fields across all 10 cities:

Field	Description
permitNumber	Official permit identifier from the source city
permitType	Type/category of permit (new build, alteration, etc.)
status	Current permit status
description	Work description / scope text
address	Street address of the permitted work
city	City the address is in
state	US state
zip	ZIP / postal code
valuation / estimatedCost	Declared project value or estimated cost
contractorName	Contractor on the permit (where the city publishes it)
applicant	Applicant / filer on the permit
issuedDate	Date the permit was issued
filedDate	Date the permit was filed / applied
latitude	Latitude of the site
longitude	Longitude of the site
sourceCity	Which of the 10 source portals the record came from
permitUrl	Link back to the record on the source portal

Note: not every city publishes every field. contractorName, applicant, and valuation/estimatedCost availability varies by source portal - the actor fills what the city exposes and leaves the rest empty rather than inventing data.

Input / How to query

Configure a run with these filters and modes:

• Cities - choose one, several, or all 10 supported portals
• Valuation min / max - keep only projects above or below a dollar threshold
• Keyword - match against the permit description (e.g. roof, solar, remodel)
• Contractor name - filter to permits tied to a specific contractor
• Date range - restrict by filed or issued date
• Multi-city pull - fetch several cities in a single run; each city's raw fields are normalized into the shared schema automatically

Results land in the run's dataset, exportable as CSV, JSON, Excel, or via the Apify API.

Example use cases

• Roofing / solar / HVAC lead gen - keyword-filter for roof, solar, HVAC, or re-roof across your target cities and pull fresh permits with addresses to build a call list.
• Contractor competitive tracking - filter by a competitor's contractorName to see where and what they're building.
• Material supplier timing - filter by valuation to surface large new-construction projects the moment they're filed, then reach out before the concrete order is placed.
• Real-estate / proptech enrichment - use latitude/longitude and address to join permit activity onto your property database.
• Market research - pull all cities over a date range to measure construction volume and mix by permitType and valuation.

Recurring use / scheduling

Set up an Apify Schedule (for example, a daily or weekly cron) so the actor re-runs on its own and captures newly filed and newly issued permits without manual effort - ideal for monitoring new building permits in a sales territory.

For clean, no-duplicate feeds:

• Use the date-range filter to only pull records since your last run.
• Point runs at the same named dataset and dedupe downstream on permitNumber + sourceCity (unique per city).
• Wire an integration (webhook, Google Sheets, Slack, or your CRM) to push each new batch straight into your workflow.

FAQ

How do I get building permit data for construction leads?

Run this actor against the cities you sell into, optionally filter by keyword, valuation, or date, and export the dataset to CSV or push it to your CRM. Each row includes the address, permit type, dates, and - where the city publishes it - the contractor and applicant, which is exactly the contact-and-context data lead-gen teams need.

Which US cities publish building permits as open data?

This actor covers 10 official portals: Chicago, San Francisco, New York City (DOB NOW), Austin, Seattle, Los Angeles, Baton Rouge, Cincinnati, Mesa, and Marin County. All are public Socrata open-data sources.

How can I scrape building permits from multiple cities into one format?

That is the core feature. Select multiple cities in one run and the actor maps each portal's differently-named columns into the same normalized schema, so every record shares the same fields regardless of source city.

How do I find new construction and renovation permits daily?

Schedule the actor to run daily and filter by filed or issued date so each run only returns recent records. Combine with a keyword like new or addition to focus on new construction and renovations.

Can I get building permit data with contractor and applicant names?

Where the source city publishes them, yes - the output includes contractorName and applicant. Coverage of these fields varies by city; portals that expose them are mapped through, and those that don't are left blank rather than guessed.

What is the best building permits API for contractors?

For contractors who want a wide, normalized feed across many cities without managing a different integration per portal, this actor works as a pay-per-result building permits API: one input schema, one output schema, 10 cities, filterable by valuation, keyword, contractor, and date.

How do I export building permit data to CSV or Excel?

Results go to the run's Apify dataset, which exports to CSV, Excel, JSON, or XML with one click, or via the Apify API for automated pipelines.

How do I monitor new building permits in my sales territory?

Pick the cities in your territory, set a schedule, filter by date range so each run is incremental, and route the output to Google Sheets, a webhook, or your CRM. Dedupe on permitNumber + sourceCity to keep the feed clean.

Is building permit data free and legal to scrape?

The underlying records come from official municipal open-data portals published for public use. This actor reads those public datasets; you are responsible for complying with each portal's terms and any applicable usage rules.

How do roofers, solar, and HVAC companies find permit leads?

They keyword-filter permit descriptions for terms like roof, solar, PV, or HVAC, restrict to their service-area cities and a recent date range, and pull the resulting addresses as a fresh lead list - then schedule it to repeat.

How do I filter building permits by valuation or project cost?

Use the valuation min and max inputs. Set a minimum to focus on large projects, a maximum to focus on small jobs, or both to target a specific project-size band.

What is a cheaper alternative to Shovels, PermitGrab, or Construction Monitor?

Instead of a fixed monthly SaaS subscription, this actor runs on Apify's pay-per-result model - you pay for the permits you actually pull across the 10 covered cities, with the same core lead fields (address, contractor where available, valuation, dates) and full control over filtering and scheduling.

Data source & notes

• Source: 10 official US city Socrata open-data portals - Chicago, San Francisco, New York City (DOB NOW), Austin, Seattle, Los Angeles, Baton Rouge, Cincinnati, Mesa, and Marin County.
• Public data: all records originate from public municipal open-data datasets. Respect each portal's terms of use.
• Field coverage varies by city. contractorName, applicant, and valuation/estimatedCost are only populated where the source city publishes them; the actor never fabricates values.
• Coverage: the 10 listed cities only - this actor does not cover every US municipality, and permit freshness depends on how often each city updates its open-data portal.
• Slug: us-building-permits-scraper · Actor ID: EvCD8QyPV2uMbPG6U