# Building Permits Scraper — Construction & Contractor Leads (`chorelet/building-permits-scraper`) Actor

Building permits from ten US and Canadian city portals in one schema: number, type, status, description, address, coordinates, applied and issued dates, declared value, units, contractor and applicant. NYC, Chicago, LA, SF, Seattle, Austin, Cincinnati, Calgary, Edmonton, Winnipeg.

- **URL**: https://apify.com/chorelet/building-permits-scraper.md
- **Developed by:** [Chorelet](https://apify.com/chorelet) (community)
- **Categories:** Lead generation, Business, Automation
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.70 / 1,000 permits

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Building Permits Scraper — Construction & Contractor Leads

**Construction and contractor leads from building permit data**, pulled from ten city open-data portals and merged into one schema: New York, Chicago, Los Angeles, San Francisco, Seattle, Austin, Cincinnati, Calgary, Edmonton and Winnipeg. Permit number, type and work class, status, the description of the work, full address with coordinates, applied and issued dates, declared value, housing units, square feet, and the contractor and applicant behind it.

Every portal names its columns differently — `permitnum` here, `job__` there, `permit_nbr` somewhere else — and this Actor maps all of them onto the same twenty-five columns, so one spreadsheet covers ten cities.

No API key, no account: these are the cities' own open-data endpoints.

### Why this Actor

- **Ten cities, one schema.** Every portal names its columns differently; this Actor maps them onto the same twenty-five, so a sweep across New York, Chicago and Calgary lands in one spreadsheet.
- **Built for a schedule.** *Only new since the last run* remembers what each city has already returned, so a daily run is a clean list of permits filed since yesterday — the shape a lead list actually needs.
- **Contractors, not just addresses.** The company on the permit is the lead — suppliers, roofers and equipment rental buy exactly this list, and it is published the day the permit is issued.
- **Current by default.** Results come back newest first and the date filter runs on the portal's side, so `30 days` is one fast request per city rather than a crawl through a decade.
- **No key and no quota.** These are the cities' own open-data endpoints, which also means the data is free to reuse.

### Sample output

One item of the dataset (long values shortened):

*See the Output tab of any run.*

### What you get

- **Fresh permits, newest first.** A run with *Issued since* `30 days` returns this month's permits — New York permits issued yesterday came back with the contractor's company name and a $50,000 declared value in testing
- **The contractor and the applicant** on every row where the city publishes them, which is what turns a permit feed into a lead list for suppliers, roofers, solar installers and equipment rental
- **Filters that matter**: keyword over the whole record, permit type, status, minimum declared value, and a contractor name to watch a single competitor across cities
- **One schema for ten cities**, with the city, portal and dataset named on every row so a number can always be traced back
- Coordinates where the portal has them, addresses assembled from house number and street where it does not

**Only new since the last run.** Turn it on and the Actor remembers the permits it has already returned for each city and starts the next run there — a daily schedule becomes a feed of permits filed since yesterday, with no duplicates to filter out and nothing charged on a quiet day. Cities enter permits a day or two late, so a watching run re-reads a three-day overlap and drops what it has seen before. The state lives in a key-value store on your own account, one per task.

Dates are normalised to plain days, values to numbers, and shouting addresses (`100 MAIN ST`) to readable ones.

### Input example

```json
{
  "cities": [
    "new-york",
    "chicago"
  ],
  "issuedSince": "30 days",
  "onlyNew": false,
  "minValue": 0,
  "maxResultsPerCity": 200
}
```

### How much does it cost?

Pay per permit — no subscription, no minimum, no charge for platform usage.

| Volume | Price |
|---|---|
| 1,000 permits | $1.00 |
| 10,000 permits | $10.00 |
| 100,000 permits | $100.00 |

The Apify **free plan includes $5 of usage every month** — about 5,000 permits with this Actor, no card needed. Nothing else is charged: platform usage is included in the price, and Apify Bronze, Silver and Gold subscribers get 10%, 20% and 30% off these prices.

### Use it from code, n8n, Make, Zapier or an AI agent

Run the Actor and download the dataset in one call (JSON by default; add `&format=csv` or `xlsx`):

```bash
curl -X POST "https://api.apify.com/v2/acts/chorelet~building-permits-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"cities": ["new-york", "chicago"], "issuedSince": "30 days", "onlyNew": false, "minValue": 0, "maxResultsPerCity": 200}'
```

Python:

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("chorelet/building-permits-scraper").call(run_input={"cities": ["new-york", "chicago"], "issuedSince": "30 days", "onlyNew": false, "minValue": 0, "maxResultsPerCity": 200})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)
```

- **n8n, Make, Zapier** — use the Apify node/module: run the Actor, then "get dataset items".
- **Google Sheets, Slack, webhooks** — add an integration on the run's *Integrations* tab.
- **AI agents** — the Actor is available as a tool through the Apify MCP server; the dataset schema describes every field for the model.
- **Schedules** — run it hourly, daily or weekly from the *Schedules* tab.

### FAQ

**Which cities are covered?**

New York, Chicago, Los Angeles, San Francisco, Seattle, Austin, Cincinnati, Calgary, Edmonton and Winnipeg. Each one was checked for permits issued in the last days — portals that stopped publishing years ago were left out on purpose.

**Can I get only the permits that appeared since my last run?**

Yes — switch on *Only new since the last run*. The Actor remembers the permit numbers it returned per city in a key-value store on your account and re-reads a three-day overlap, because cities enter permits late. Quiet days cost only the run start.

**Why is the contractor empty for some cities?**

Not every portal publishes it. New York, Chicago, Calgary and Cincinnati do; Seattle and Austin do not. The column is there either way so the shape never changes.

**How far back can I go?**

As far as the portal keeps records — most hold a decade or more. Set *Issued since* to a date instead of a relative window, and raise the per-city cap.

**Can I watch one builder across cities?**

Yes — put their name in *Contractor or applicant* and list several cities. Matching is partial and case-insensitive.

**Is the declared value reliable?**

It is what the applicant declared, which is a good relative signal and a poor absolute one. Some permits declare nothing, which is why the minimum-value filter keeps zero-value rows unless you raise it.

**Do I need an API key?**

No. Each city publishes through an open Socrata endpoint that answers without a token.

### Support

Questions, missing fields or a source that changed? Open an issue on the *Issues* tab or write to support@chorelet.app — problems are usually fixed within a day, and the Actor is checked every morning by an automated test run. If the Actor saved you time, a short review on its Store page helps other people find it.

# Actor input Schema

## `cities` (type: `array`):

Supported: new-york, chicago, san-francisco, seattle, los-angeles, austin, cincinnati, calgary, edmonton, winnipeg. Names and nicknames work too — `New York`, `NYC`, `San Francisco`.

## `issuedSince` (type: `string`):

`30 days`, `last 6 months` or a date such as `2026-01-01`. This is what keeps a run small and current.

## `issuedUntil` (type: `string`):

Same formats; leave empty for today.

## `onlyNew` (type: `boolean`):

Saves only permits that earlier runs did not return. The state is kept in a key-value store on your own account and the run re-reads a three-day overlap, because cities enter permits a day or two late. A run that finds nothing new costs only the run start.

## `watchKey` (type: `string`):

Which saved state to continue. Empty = one state per task, so two schedules of this Actor never overwrite each other. Set it by hand to share one state between tasks, or change it to start over.

## `keyword` (type: `string`):

Full-text search over the permit record — `solar`, `pool`, `roof`, `kitchen`.

## `permitTypes` (type: `array`):

Partial matches against the permit type, class or work class: `electrical`, `new construction`, `demolition`.

## `statuses` (type: `array`):

Partial matches against the status: `issued`, `final`, `expired`.

## `contractor` (type: `string`):

Keeps only permits whose contractor or applicant contains this text — the way to watch a competitor.

## `minValue` (type: `integer`):

In the city's own currency. 0 keeps everything, including the permits that declare nothing.

## `maxResultsPerCity` (type: `integer`):

Newest first, so a small cap still gives you this week's permits.

## Actor input object example

```json
{
  "cities": [
    "new-york",
    "chicago"
  ],
  "issuedSince": "30 days",
  "onlyNew": false,
  "watchKey": "",
  "permitTypes": [],
  "statuses": [],
  "minValue": 0,
  "maxResultsPerCity": 200
}
```

# Actor output Schema

## `permits` (type: `string`):

Everything scraped — items of the default dataset. Use ?format=csv or xlsx on this URL for spreadsheets.

## `summary` (type: `string`):

Permits per city, what the filters dropped and any errors.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "cities": [
        "new-york",
        "chicago"
    ],
    "issuedSince": "30 days",
    "issuedUntil": "",
    "onlyNew": false,
    "watchKey": "",
    "keyword": "",
    "permitTypes": [],
    "statuses": [],
    "contractor": "",
    "minValue": 0,
    "maxResultsPerCity": 200
};

// Run the Actor and wait for it to finish
const run = await client.actor("chorelet/building-permits-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "cities": [
        "new-york",
        "chicago",
    ],
    "issuedSince": "30 days",
    "issuedUntil": "",
    "onlyNew": False,
    "watchKey": "",
    "keyword": "",
    "permitTypes": [],
    "statuses": [],
    "contractor": "",
    "minValue": 0,
    "maxResultsPerCity": 200,
}

# Run the Actor and wait for it to finish
run = client.actor("chorelet/building-permits-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "cities": [
    "new-york",
    "chicago"
  ],
  "issuedSince": "30 days",
  "issuedUntil": "",
  "onlyNew": false,
  "watchKey": "",
  "keyword": "",
  "permitTypes": [],
  "statuses": [],
  "contractor": "",
  "minValue": 0,
  "maxResultsPerCity": 200
}' |
apify call chorelet/building-permits-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,chorelet/building-permits-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/1757jTtPrvlEROrIs/builds/8K2z0dm5IOLLckq9F/openapi.json