# Austin Permit Leads: Demolitions, New Builds & New Pools (`ralarcon/austin-permit-leads`) Actor

Daily sales leads from official City of Austin building permits: demolitions and new builds for dumpster, portable toilet and temporary fence companies; new pools for pool fence, pool service and landscaping companies.

- **URL**: https://apify.com/ralarcon/austin-permit-leads.md
- **Developed by:** [Rodrigo Alarcón](https://apify.com/ralarcon) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $30.00 / 1,000 lead delivereds

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

## Austin Permit Leads: Demolitions, New Builds & New Pools

Get fresh, scored sales leads from **official City of Austin, TX building permits**, packaged for the businesses that sell *after* the permit is issued.

The contractor who pulled the permit already won the job. The opportunity is for the trades that project needs next. This Actor turns the city's daily permit feed into two ready-to-use lead lists:

| Lead type | What's included | Who buys it |
|---|---|---|
| **Site services** | Total demolitions and new residential/commercial builds | Roll-off dumpster rental, portable toilets, temporary construction fencing, site cleanup |
| **New pools** | New in-ground pools and spas (residential and commercial) | Pool fence installers, weekly pool service, landscaping, decks and outdoor living |

### Why these leads are different

- **One lead per project, not per permit.** A new pool usually has building, electrical and plumbing permits. We group them by address so you never pay three times for the same job.
- **Hand-validated classification.** Rules were checked against real Austin permits: 93%+ precision on site services and 100% on new pools in our review samples. Bathroom remodels that mention "demo", gates, partial demolitions, pool repairs and pool decks are filtered out.
- **The right contact.** For new pools we look up the **pool builder**, not just the electrician or plumber who pulled a trade permit.
- **Large builders flagged.** Production builders with 25+ new builds a year usually have fixed vendors. Flag them or exclude them in one click. Demolitions are always kept.
- **Company phones only.** We return contractor and builder business phones. We never return private homeowner phone numbers.
- **Pay only for new leads.** Turn on *Only new leads since my last run* and schedule the Actor daily or weekly.

### Output

Each lead includes:

| Field | Example |
|---|---|
| `score` (0–100) and `scoreReasons` | `91`, `["demolition always generates debris", "small/independent builder", "company phone available", "issued 2 day(s) ago"]` |
| `leadType` | `demolition`, `new_residential`, `new_commercial`, `residential_pool`, `commercial_pool` |
| `issuedDate`, `address`, `zip`, `latitude`, `longitude` | `2026-09-26`, `2207 DE VERNE ST`, `78704` |
| `workDescription` | `Total Demo of SFR 1100 Sqft circa 1953` |
| `contractorName`, `contractorPhone` | `DAR Construction`, `(512) 453-4646` |
| `poolBuilderName`, `poolBuilderPhone` | new pools only |
| `valuationUsd`, `isLargeBuilder`, `permitsAtAddress` | |
| `sourceUrl` | link to the permit on the City of Austin portal |

Download as CSV, Excel or JSON, or send it to your CRM with Apify integrations (Zapier, Make, webhooks, Google Sheets).

### How to use

1. Choose the **Lead type**.
2. Optionally list the **ZIP codes** you serve.
3. Set **Days back** (7 for a weekly run, 1 for daily).
4. For a recurring feed, turn on **Only new leads since my last run** and create a schedule.

### Pricing

You pay per lead delivered. Set a maximum per run with **Max leads per run** or with Apify's spending limit. Leads are sorted best-first, so a limit always gives you the highest-scoring ones.

### Coverage and data source

City of Austin full-purpose jurisdiction, from the official *Issued Construction Permits* open dataset (updated daily, public domain). Permits issued by surrounding cities and counties are not included yet.

### Responsible use

Permit data is public record. Contacts are business contacts of licensed contractors. Follow applicable US telemarketing and email rules (TCPA, Do Not Call, CAN-SPAM) in your outreach. Data is provided as published by the city; verify details before making business decisions.

# Actor input Schema

## `product` (type: `string`):

Which leads you want. Site services: demolitions and new builds (for dumpster, portable toilet and temporary fencing companies). New pools: new residential and commercial pools and spas (for pool fence, pool service, landscaping and deck companies).

## `daysBack` (type: `integer`):

Include permits issued in the last N days. Use 1–7 for a daily or weekly schedule, up to 365 for a backfill.

## `zipCodes` (type: `array`):

Only return leads in these ZIP codes. Leave empty for all of Austin.

## `subtypes` (type: `array`):

Optional. Site services: demolition, new\_residential, new\_commercial. New pools: residential\_pool, commercial\_pool. Leave empty for all.

## `excludeLargeBuilders` (type: `boolean`):

Site services only. Skip new builds by builders with 25+ new-build permits in the last year (they usually have fixed vendors). Demolitions are always kept.

## `includeCommercial` (type: `boolean`):

Include commercial buildings and commercial/multifamily pools.

## `onlyWithPhone` (type: `boolean`):

Skip leads without a contractor or builder phone number.

## `onlyNewSinceLastRun` (type: `boolean`):

Remember delivered leads and skip them next time. Turn this on when you run the Actor on a schedule, so you never pay twice for the same lead.

## `maxLeads` (type: `integer`):

Upper limit of leads delivered (and charged) in one run. Leads are sorted by score, best first.

## `socrataAppToken` (type: `string`):

Optional free token from data.austintexas.gov to avoid rate limits on large backfills.

## Actor input object example

```json
{
  "product": "site_services",
  "daysBack": 7,
  "zipCodes": [
    "78704",
    "78744",
    "78745"
  ],
  "excludeLargeBuilders": false,
  "includeCommercial": true,
  "onlyWithPhone": false,
  "onlyNewSinceLastRun": false,
  "maxLeads": 500
}
```

# Actor output Schema

## `leads` (type: `string`):

Scored leads with address, work description, contractor, phone and pool builder, best first.

# 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 = {
    "zipCodes": [
        "78704",
        "78744",
        "78745"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ralarcon/austin-permit-leads").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 = { "zipCodes": [
        "78704",
        "78744",
        "78745",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("ralarcon/austin-permit-leads").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 '{
  "zipCodes": [
    "78704",
    "78744",
    "78745"
  ]
}' |
apify call ralarcon/austin-permit-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ralarcon/austin-permit-leads"
        }
    }
}
```

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/QhqxAaz8odHssmcuZ/builds/gKX2b4f9or34cYvKy/openapi.json