# Cloudpermit Scraper: Building Permits & Code Enforcement (`pantherjaboba/cloudpermit-public-records`) Actor

Scrape building permits, code-enforcement cases, land-use and planning records from any town that publishes on Cloudpermit (US + Canada). Address, parcel, status, dates, coordinates, project details.

- **URL**: https://apify.com/pantherjaboba/cloudpermit-public-records.md
- **Developed by:** [Jeremiah Davis](https://apify.com/pantherjaboba) (community)
- **Categories:** Lead generation, Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Cloudpermit Public Records Scraper

Get **building permits, code-enforcement cases, land-use and planning records** from any US or Canadian town that publishes on **Cloudpermit**. That's hundreds of small and mid-size municipalities that the big "open data" permit scrapers don't cover.

Paste a portal URL or name and get clean, structured records:

| Field | Example |
|---|---|
| `jurisdiction` | City of Bingen |
| `record_type` | Building Permits / Code Enforcement / Land Use / Planning Approval |
| `municipal_case_id` | CB-26-032 |
| `status` | permit-issued, construction-started, … |
| `project_name` | New Roof |
| `categories` | \["Reroof"] |
| `work_types` / `work_targets` | \["Residential"] / \["New"] |
| `description` | Case description (code enforcement) |
| `address` | 524 W LINCOLN |
| `parcel_id` | 03113055011102 (join to county tax/owner data) |
| `latitude` / `longitude` | 45.7192, -121.4699 |
| `created_date` / `submitted_date` / `issued_date` | 2026-09-10 |
| `property_owners` / `applicants` | optional, off by default |

### Who uses this

- **Contractors & home-service companies** (roofing, solar, HVAC, pools, fencing): new permits = homeowners actively spending on their property.
- **Real-estate investors**: code-enforcement cases (condemnation, minimum housing, vacant, junk) are classic motivated-seller signals.
- **Suppliers, insurers, analysts, journalists**: construction activity and enforcement trends in small towns.

### How to use

1. **Portals**: find a town's portal at `https://us.cloudpermit.com/<name>/public-records` (Canada: `ca.cloudpermit.com`). Enter the URL or just `<name>`; for Canada use `ca:<name>`.
2. **Record types** (optional): `B` building, `CE` code enforcement, `LU` land use, `P` planning. Leave empty for everything the town publishes. The run log lists each town's types.
3. **Created on or after** (optional): set this and **schedule the actor daily or weekly** to get only new records, which works as a lead alert feed.
4. **Max records per portal** (optional): newest first.

Example input:

```json
{
  "portals": ["bingen", "https://us.cloudpermit.com/hendersonvillenc/public-records"],
  "recordTypes": ["B", "CE"],
  "createdAfter": "2026-09-01"
}
```

### Pricing

Pay per result: you only pay for records delivered. Set a max charge in the run options and the actor stops cleanly at your limit.

### Notes

- Data comes from each town's own **public** Cloudpermit records page. No login, no CAPTCHA bypass.
- Which fields exist depends on what each town chooses to publish.
- Owner/applicant names are personal data and are **off by default**. Enable them only with a legitimate purpose and in line with the laws that apply to you (e.g. TCPA/CAN-SPAM for outreach).
- A town isn't found? Check the portal name in its Cloudpermit URL. The run's status message lists any that failed.

# Actor input Schema

## `portals` (type: `array`):

Towns to scrape. Paste the portal URL (e.g. https://us.cloudpermit.com/bingen/public-records) or just the portal name (bingen). Canadian portals: ca:gravenhurst or the ca.cloudpermit.com URL.

## `recordTypes` (type: `array`):

Optional. Codes to include, e.g. B (building permits), CE (code enforcement), LU (land use), P (planning). Empty = every type the town publishes.

## `createdAfter` (type: `string`):

Optional. Only records created on/after this date (YYYY-MM-DD). Use it for daily/weekly monitoring runs.

## `maxItemsPerPortal` (type: `integer`):

Optional cap per town (newest first). 0 = no cap, i.e. the town's full history.

## `includePersonalNames` (type: `boolean`):

Adds property owner and applicant names where the town publishes them. Personal data: only enable if you have a legitimate reason and comply with applicable law.

## Actor input object example

```json
{
  "portals": [
    "bingen",
    "hendersonvillenc"
  ],
  "recordTypes": [],
  "maxItemsPerPortal": 50,
  "includePersonalNames": false
}
```

# Actor output Schema

## `records` (type: `string`):

All records from this run: town, record type, case number, status, address, project, categories, created/issued dates, parcel ID and coordinates. Owner and applicant names only when includePersonalNames is on.

# 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 = {
    "portals": [
        "bingen",
        "hendersonvillenc"
    ],
    "maxItemsPerPortal": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("pantherjaboba/cloudpermit-public-records").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 = {
    "portals": [
        "bingen",
        "hendersonvillenc",
    ],
    "maxItemsPerPortal": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("pantherjaboba/cloudpermit-public-records").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 '{
  "portals": [
    "bingen",
    "hendersonvillenc"
  ],
  "maxItemsPerPortal": 50
}' |
apify call pantherjaboba/cloudpermit-public-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pantherjaboba/cloudpermit-public-records"
        }
    }
}
```

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/9vykaTyY7ElTUCuRT/builds/00O5Kat4NtbeKXwJf/openapi.json