# New Home Builder Leads – Collin County TX Building Permits (`leadsignal-data/collin-county-tx-building-permits`) Actor

Building permits across Collin County, Texas (McKinney, Allen, Frisco, Plano, Prosper, Princeton, Anna, Wylie…) from the Collin Central Appraisal District: builder, plan, permit value, property owner, address and subdivision. Only new leads each run.

- **URL**: https://apify.com/leadsignal-data/collin-county-tx-building-permits.md
- **Developed by:** [Alex](https://apify.com/leadsignal-data) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.00 / 1,000 results

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

## New Home Builder Leads: Collin County, TX Building Permits

**Building permits from across Collin County, one of the fastest-growing counties in the US, including McKinney, Allen, Princeton, Anna, Wylie, Prosper, Frisco, Plano and Celina. Each lead has the builder, plan, permit value and property owner. About 2¢ each.**

Cities report their permits to the **Collin Central Appraisal District (CAD)**, and this Actor reads the CAD's official permit file on data.texas.gov, which is refreshed daily. Recent months average **2,000–2,600 permits a month**. About half are **new construction**, and the rest are pools, roofs, solar, remodels, additions and finish-outs. Each lead includes the permit number, issue date, issuing city, permit type, **builder name and floor plan**, declared permit value, **property owner** (often the builder's land LLC), situs address, ZIP, subdivision and legal description.

👉 **Try it free:** new Apify accounts get **$5 of free platform credit every month**.

### Real sample leads (pulled October 2026)

| Builder | City | Address | Permit value | Owner | Issued |
|---|---|---|---|---|---|
| Shaddock | Allen | 208 Ardsley Way | $1,343,640 | Shaddock-Custer Ridge LLC | 2026-10-07 |
| Shaddock | Allen | 211 Kings Hollow Pl | $1,243,910 | Shaddock-Custer Ridge LLC | 2026-10-07 |
| Southgate | Allen | 2109 Spiderlilly Ln | $433,200 | SGHDAL LLC | 2026-10-07 |
| Southgate | Allen | 986 Coreopsis Dr | $416,100 | SGHDAL LLC | 2026-10-07 |
| Commercial Bldg | Murphy | 109 E Betsy Ln | $1,965,000 | Betsy Properties LLC | 2026-09-30 |

**ROI:** 1,000 permits cost $20. One builder account for flooring, cabinets, garage doors or landscaping can be worth six figures.

### Who uses it

Suppliers that sell to builders (flooring, cabinets, countertops, garage doors, fencing, irrigation) · subcontractors · title, mortgage and insurance · home-services and security companies targeting new homeowners · land and market analysts tracking builder activity.

### Filters

**Cities** (`McKinney`, `Allen`, `Frisco`, `Prosper`, `Princeton`) · **ZIPs** · **permit types** (`New Construction`, `Pool`, `Roof/Re-Roof`, `Solar Energy Device`, `Finish Out`) · **property use** (residential/commercial) · **builder keywords** (`Shaddock`, `Trophy`, `Highland`) · **minimum permit value** · issue-date range.

### Set it up as a daily lead feed

Keep **Only new since last run** on, choose **Schedule → Daily**, and send leads to Google Sheets, HubSpot, Slack, Zapier or Make. Cities send permits to the CAD in batches, so some permits show up days or weeks after their issue date. With dedupe on, a daily run picks up those late arrivals without repeating anything you already have.

### Input

```json
{ "cities": ["McKinney", "Allen", "Prosper"], "permitTypes": ["New Construction"], "dateFrom": "30 days", "onlyNew": true }
```

### Output fields

`permitNumber, permitId, issuedDate, permitType, permitSubtype, issuedBy, issuedTo, builder, builderPlan, permitValue, buildingArea, propertyUse, ownerName, address, city, state, zip, subdivision, legalDescription, comments, propertyId, source`

### Pricing

Pay per result: **$0.02 per lead** ($20 per 1,000). No subscription.

### FAQ

**Where does the data come from?** The "Collin CAD Building Permits" dataset on data.texas.gov, published by the Collin Central Appraisal District.
**Why do Plano and Frisco show few permits?** Each city decides what it reports to the CAD. Most of the volume comes from McKinney, Allen, Princeton, Anna, Wylie and unincorporated Collin County.
**Why is the permit value sometimes empty?** Some cities report $0. Use "Minimum permit value" to keep only valued permits.
**Phone numbers?** The CAD doesn't publish them. Builder and owner names are easy to enrich.

***

*Last updated: October 14, 2026 · Built by **LeadSignal**: public-record lead feeds for B2B sales. Not affiliated with the Collin Central Appraisal District or the State of Texas.*

# Actor input Schema

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

e.g. McKinney, Allen, Frisco, Plano, Prosper, Princeton, Anna, Wylie, Celina. Empty = all of Collin County.

## `zips` (type: `array`):

e.g. 75013, 75071.

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

New Construction, Miscellaneous, Roof/Re-Roof, Pool, Pool & Spa, Solar Energy Device, Accessory Building, Remodeling, Addition, Finish Out, Demolition.

## `propertyUse` (type: `string`):

Residential or commercial parcels only.

## `builderKeywords` (type: `array`):

Match the builder name, e.g. Shaddock, Trophy, Highland, Perry, Lennar.

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

Only permits with a declared value at or above this (many cities report 0).

## `dateFrom` (type: `string`):

YYYY-MM-DD or relative like '30 days'.

## `dateTo` (type: `string`):

YYYY-MM-DD

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

Skip leads already returned by previous runs (ideal for scheduled daily feeds).

## `dedupeStoreName` (type: `string`):

Named key-value store used to remember seen leads. Use different names for different feeds.

## `maxItems` (type: `integer`):

Maximum leads to return in this run.

## Actor input object example

```json
{
  "cities": [
    "McKinney",
    "Allen"
  ],
  "permitTypes": [
    "New Construction"
  ],
  "propertyUse": "Any",
  "dateFrom": "30 days",
  "onlyNew": true,
  "dedupeStoreName": "collin-county-tx-building-permits-seen",
  "maxItems": 1000
}
```

# Actor output Schema

## `results` (type: `string`):

All leads/records returned by this run.

# 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": [
        "McKinney",
        "Allen"
    ],
    "permitTypes": [
        "New Construction"
    ],
    "dateFrom": "30 days"
};

// Run the Actor and wait for it to finish
const run = await client.actor("leadsignal-data/collin-county-tx-building-permits").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": [
        "McKinney",
        "Allen",
    ],
    "permitTypes": ["New Construction"],
    "dateFrom": "30 days",
}

# Run the Actor and wait for it to finish
run = client.actor("leadsignal-data/collin-county-tx-building-permits").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": [
    "McKinney",
    "Allen"
  ],
  "permitTypes": [
    "New Construction"
  ],
  "dateFrom": "30 days"
}' |
apify call leadsignal-data/collin-county-tx-building-permits --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leadsignal-data/collin-county-tx-building-permits"
        }
    }
}
```

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/Dj5rxIMOHu8mBQD8e/builds/3zMVV4yaUApeR8MXI/openapi.json