DWA Open Data · data APIs on Apify
PERMITS · Leads & companies

Building Permits Leads: New Construction Permits by City

Construction permit feed from official city open-data portals (Chicago, NYC, LA, SF, Seattle, Austin, Baton Rouge, Montgomery Co. MD, Cincinnati). Returns type, status, dates, valuation, property address, contractor business if published, source link, and code violations. Delta mode available.

Who it is for

Sales, growth and RevOps teams building prospect lists, and agencies feeding a CRM with fresh, structured company data.

Pricing

EventPricePer 1,000
Permit or violation recordCharged once per permit or code-violation record delivered to the dataset (after filters and delta dedupe against previous runs). Records skipped as already-seen or filtered out are never charged.--
Actor StartCharged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).$0.00005-

Prices are read live from the Apify listing at build time. Apify platform usage is included in event prices.

Sample output

permitIdrecordTypecityCodecitystate
101090772permitCHIChicagoIL
101090774permitCHIChicagoIL

First rows of a real run, selected columns. Emails, phone numbers and personal names are masked. Full output has more fields.

Input

  • cities · Cities: Which city portals to query. Permits: CHI, NYC, LAX, SFO, SEA, AUS, BTR, MOCO. Code violations: CHI, CIN. Empty = all nine.
  • city · City (single, plain name): Optional shortcut for one city, for example Chicago, Seattle, Austin, New York or a city code such as CHI. It is added to the Cities list. Supported: CHI, NYC, LAX, SFO, SEA, AUS, BTR, MOCO, CIN.
  • recordTypes · Record types: permit = building permits; violation = code-enforcement / building violations (only CHI and CIN publish these here).
  • sinceDays · Since days: Return records whose issue date (filing date for San Francisco, violation date for violations) falls in the last N days (1 to 180).
  • dateFrom · Issued from (date): Start of the date window, YYYY-MM-DD. When set it replaces Days to look back, so you can pull any period the city portal still holds.
  • dateTo · Issued to (date): End of the date window, YYYY-MM-DD. Defaults to today.
  • maxItems · Max items: Cap on records delivered (and charged) this run, split evenly across the selected city sources.
  • keywords · Permit type / work keywords: Keep only records whose type, work class or description contains any of these words (case-insensitive), e.g. roof, solar, demolition, new construction, hvac.
  • keyword · Keyword (single): Optional single keyword searched in the permit description and work class, for example solar, demolition or roof. Added to the Keywords list.
  • permitTypes · Permit types: Keep only permits whose permit type or work class contains any of these words, for example ["electrical","new construction","demolition"]. Matching is by substring and the exact type names differ by city.

Use it from an AI agent (MCP)

Add this server URL to Claude, Cursor, VS Code or any MCP client. Authenticate with your Apify account.

https://mcp.apify.com/?tools=transparent_meteorite/building-permits-leads

FAQ

How do I run Building Permits Leads: New Construction Permits by City?

Open it on Apify, fill in the input form, and press Start. You can also call it from the Apify API, a schedule, or an AI agent via MCP. Results land in a dataset you can download as JSON, CSV or Excel.

How is it billed?

Pay-per-event on Apify: you are charged only for the events listed in the price table above, plus nothing else from this listing. There is no subscription.

Where does the data come from?

Only publicly available sources. The Actor does not log in to any account or bypass access controls.

Can I use it from an AI assistant?

Yes. Add the MCP URL shown above to any MCP-capable client (Claude, Cursor, VS Code and others) and the Actor becomes a callable tool.