# New Construction Leads – Austin Permits with Contractor Phones (`leadsignal-data/austin-new-construction-permits`) Actor

Newly issued City of Austin new-construction permits: homes, multifamily, commercial. Contractor company, name and phone, applicant, valuation, sq ft, units, address. Official open data, remodels and repairs excluded. Only new leads each run.

- **URL**: https://apify.com/leadsignal-data/austin-new-construction-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 Construction Leads – Austin Permits with Contractor Phones

**Every new home, multifamily and commercial build permitted in Austin, with the contractor's phone number. About 2¢ a lead.**

This feed comes from the **City of Austin Development Services Department's** Issued Construction Permits dataset, filtered to work class **New**, so remodels, repairs and change-outs never show up. That's about **360 new-construction building permits a month**. Each lead has the job address, permit class, square footage, floors, housing units, declared valuation, plus the **contractor company, contact name and phone** and the applicant's details. Voided and withdrawn permits are filtered out.

👉 **Try it free:** new Apify accounts get **$5 of free platform credit every month**, enough for hundreds of leads. Click **Try for free**, set your filters and hit Start.

### Real sample leads (pulled October 2026)

| Address | Class | Contractor | Phone | Issued |
|---|---|---|---|---|
| 2204 Alexander Ave Bldg 1 | R- 103 Two Family Bldgs | A R Lucas Construction LLC | 512-965-3773 | 2026-10-12 |
| 2204 Alexander Ave Bldg 2 | R- 103 Two Family Bldgs | A R Lucas Construction LLC | 512-965-3773 | 2026-10-12 |
| 6307 West Courtyard Dr | R- 329 Res Structures Other Than Bldg | Driftwood Custom Pools LLC | 512-784-0954 | 2026-10-12 |
| 7901 Fm 2222 Rd | C- 329 Com Structures Other Than Bldg | The Burt Group | 512-275-0881 | 2026-10-12 |
| 2811 Rock Terrace Dr | R- 329 Res Structures Other Than Bldg | Thomas Randolph Excavation, LLC | 512-662-1231 | 2026-10-12 |

**ROI:** 1,000 new Austin builds cost $20. One supply account, subcontract or insurance policy pays for years of runs.

### Who uses it

Subcontractors (framing, concrete, roofing, HVAC, plumbing, electrical) · lumber yards, building supply & equipment rental · windows, doors, cabinets, countertops, flooring · solar, pools, landscaping, fencing · builder's risk insurance, construction lending · security, low-voltage, smart-home, internet providers · new-homeowner marketing.

### Filters

- **Permit types**: `Building Permit` by default; add `Electrical Permit`, `Plumbing Permit`, `Mechanical Permit` to get the trade permits on new builds
- **Residential / Commercial**
- **Permit class** (contains): `Single Family`, `Two Family`, `Five or More Family`, `Office`, `Retail`
- **Description keywords**: `pool`, `ADU`, `duplex`
- **ZIP codes** and **minimum valuation**
- Issue-date range

### Set it up as a daily lead feed

1. Set your filters (or leave them empty for everything).
2. Keep **Only new since last run** on. Each run returns only leads you haven't seen.
3. Click **Schedule → Daily**, then connect **Google Sheets, HubSpot, Salesforce, Slack, Zapier or Make** so fresh leads land in your tools automatically.

Runs with nothing new cost almost nothing, because you only pay for the leads you get.

### Input

```json
{"permitTypes": ["Building Permit"], "categories": ["Residential"], "zips": ["78744", "78704"], "dateFrom": "30 days", "onlyNew": true}
```

### Output fields

`permitNumber, permitType, category, permitClass, workClass, description, address, city, state, zip, councilDistrict, jurisdiction, valuation, newSqft, floors, housingUnits, appliedDate, issueDate, expiresDate, status, contractorCompany, contractorName, contractorPhone, contractorTrade, contractorAddress, contractorCity, contractorZip, applicantName, applicantOrg, applicantPhone, applicantAddress, applicantCity, applicantZip, permitUrl, latitude, longitude, source`. Export as CSV, Excel or JSON, or pull it through the API.

### Pricing

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

### FAQ

**Where does the data come from?** The "Issued Construction Permits" dataset (3syk-w9eu) on datahub.austintexas.gov, the City of Austin's official open-data portal, updated daily.
**Does it include phone numbers?** Yes. Contractor phone is present on virtually every new building permit, and applicant phone on most.
**Why is valuation empty on some rows?** Many residential permits declare a $0 or $1 valuation. We return those as empty rather than a misleading number. Use square footage and housing units to size the job.
**Is it only new construction?** Yes. Only work class "New" is returned. Remodels, additions, repairs, demolitions and change-outs are excluded.
**How do I avoid duplicates?** Keep "Only new since last run" on, and use a different dedupe store name for each separate feed.

**Need another city?** Request it in the Issues tab. LeadSignal adds new feeds regularly.

***

*Last updated: October 14, 2026 · Built by **LeadSignal**: public-record lead feeds for B2B sales. Not affiliated with the City of Austin.*

# Actor input Schema

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

Default: Building Permit (the new structure itself). Add trade permits on new builds if you want them: Electrical Permit, Plumbing Permit, Mechanical Permit, Driveway / Sidewalks.

## `categories` (type: `array`):

Residential or Commercial. Empty = both.

## `permitClassKeywords` (type: `array`):

e.g. Single Family, Two Family, Five or More Family, Office, Retail, Hotel, Pkg Garage.

## `descriptionKeywords` (type: `array`):

Match the work description, e.g. pool, ADU, duplex, restaurant.

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

e.g. 78704, 78744.

## `minValuation` (type: `integer`):

Only permits with a declared valuation at or above this. Note: many residential permits declare $0, so this filter drops them.

## `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
{
  "permitTypes": [
    "Building Permit"
  ],
  "dateFrom": "30 days",
  "onlyNew": true,
  "dedupeStoreName": "austin-new-construction-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 = {
    "permitTypes": [
        "Building Permit"
    ],
    "dateFrom": "30 days"
};

// Run the Actor and wait for it to finish
const run = await client.actor("leadsignal-data/austin-new-construction-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 = {
    "permitTypes": ["Building Permit"],
    "dateFrom": "30 days",
}

# Run the Actor and wait for it to finish
run = client.actor("leadsignal-data/austin-new-construction-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 '{
  "permitTypes": [
    "Building Permit"
  ],
  "dateFrom": "30 days"
}' |
apify call leadsignal-data/austin-new-construction-permits --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leadsignal-data/austin-new-construction-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/zm4cFts3dCVhHVjQF/builds/EwVb0njCilnRBbCAS/openapi.json