# Dallas Building Permits Scraper (`bigibyte/dallas-building-permits-scraper`) Actor

Dallas Building Permits Scraper is a Python tool to extract permit numbers, issue dates, property addresses, permit types, contractor details, and valuation estimates from city municipal databases. It exports structured construction datasets into clean CSV or JSON formats

- **URL**: https://apify.com/bigibyte/dallas-building-permits-scraper.md
- **Developed by:** [BigiByte](https://apify.com/bigibyte) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## 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

### Dallas Building Permits Scraper — Construction Permits and Contractor Records

![Dallas Building Permits Scraper cover](https://images.bigibyte.com/cdn-cgi/image/width=1260,height=540,fit=cover,format=webp/apify-actors-covers/dallas-building-permits-scraper-cover.png)

Collect public building permit records from the City of Dallas, Texas, in a structured dataset. Retrieve permit numbers, permit types, contractors, project values, property addresses, and work descriptions for construction research, contractor analysis, and real estate projects.

### Overview

This actor collects records from the City of Dallas Building Permits dataset. It supports retrieving permit records, filtering results, and inspecting available dataset fields.

The dataset contains historical permit information and may no longer receive new updates from the source.

### Features

- Collect Dallas building permit records.
- Retrieve all available rows or limit the number of records.
- Filter records using custom conditions.
- Search records using supported text queries.
- Retrieve dataset column names, types, and descriptions.
- Export results in JSON, CSV, Excel, and other supported Apify dataset formats.
- Store collected records in an Apify dataset.

### Collection Modes

| Mode | Description |
|---|---|
| `rows` | Collects building permit records. |
| `filtered` | Collects records matching specified filter conditions or search terms. |
| `metadata` | Retrieves available dataset column names, types, and descriptions. |

### Input Parameters

| Parameter | Description |
|---|---|
| `mode` | Selects the collection mode: `rows`, `filtered`, or `metadata`. |
| `maxItems` | Maximum number of records to collect. |
| `orderBy` | Field or expression used to order the results. |
| `where` | Optional filter condition for selecting specific records. |
| `requestDelaySecs` | Delay between collection requests. |

### Example Input

**Collect building permit records**

```json
{
  "mode": "rows",
  "maxItems": 50,
  "orderBy": ":id",
  "requestDelaySecs": 1
}
```

**Collect filtered records**

```json
{
  "mode": "filtered",
  "where": "value > '1000'",
  "maxItems": 25,
  "requestDelaySecs": 1
}
```

### What Data Does This Actor Extract?

The actor collects available building permit fields, including:

| Field | Description |
|---|---|
| `permit_number` | Building permit identification number. |
| `permit_type` | Permit category or type. |
| `issued_date` | Date the permit was issued. |
| `mapsco` | Mapsco location reference. |
| `contractor` | Contractor name and available contact or business details. |
| `value` | Reported project or permit value. |
| `area` | Recorded project area. |
| `work_description` | Description of the permitted work. |
| `land_use` | Land-use classification. |
| `street_address` | Property or project street address. |
| `zip_code` | Property ZIP code. |
| `scraped_at` | Date and time the record was collected. |

Field availability and values depend on the records provided by the dataset.

### Example Output

```json
{
  "permit_number": "2003133024",
  "permit_type": "Electrical (EL) Commercial Alteration",
  "issued_date": "03/13/20",
  "mapsco": "39-N",
  "contractor": "B+T GROUP HOLDINGS INC 1025 S. Belt Line Road, Suite 400, Coppell, TX 75019 (469) 480-3578",
  "value": "1800",
  "area": "0",
  "work_description": "PERMANENT ELECTRICAL SERVICE",
  "land_use": "COMMUNICATIONS",
  "street_address": "2928 ANDREA LN",
  "zip_code": "75228",
  "scraped_at": "2026-10-26T00:00:00+00:00"
}
```

### Working with Your Dataset

After the actor finishes running, open the Apify dataset to explore the collected permit records.

You can:

- Export records as JSON, CSV, or Excel.
- Filter and sort permits by issue date, type, or project value.
- Review contractor and project information.
- Group records by ZIP code or land-use category.
- Use the collected data in reporting and analysis workflows.

### Use Cases

- **Construction Lead Research:** Identify historical permit records and related contractors.
- **Contractor Research:** Explore contractor names and associated permit activity.
- **Real Estate Analysis:** Study construction activity across Dallas locations.
- **Market Research:** Analyze permit types, project values, and work descriptions.
- **Data Analysis:** Build structured datasets for research and reporting.

### FAQ

**Who can use this actor?**

Researchers, analysts, developers, contractors, and other users interested in Dallas building permit records.

**What export formats are supported?**

You can export the collected dataset in JSON, CSV, Excel, and other supported Apify dataset formats.

**Can I run the actor on a schedule?**

Yes. You can configure an Apify schedule to run the actor automatically at your preferred interval. Keep in mind that the source dataset may no longer receive new records.

**How do I filter permits by project value or contractor?**

Use `filtered` mode with an appropriate condition in the `where` parameter. You can also use supported text search to find matching records.

**Is the dataset current?**

The dataset is historical and may no longer receive updates. Check the original public records before relying on a permit as evidence of current construction activity.

### Related tools

If you plan to map or join these rows, a geocoding pass or a quick CSV cleanup are the usual next steps. BigiByte also builds scrapers for other open-data portals when you need them as a separate job. Need another open dataset, a scheduled monitor, or a custom pipeline? BigiByte builds custom scrapers and APIs: https://bigibyte.com

### Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, sponsored by, or otherwise officially associated with the City of Dallas. All data is collected from publicly available sources. Users are responsible for complying with applicable terms of use and laws when using the collected information.

### Is Web Scraping Legal?

Collecting information that is already public is generally legal. There is no single law that bans all forms of web scraping. The limits are the usual ones: do not break into accounts, do not take private or confidential data, and be careful with personal data and copyrighted works. A site's terms can also restrict how you access it. Facts such as a public name, price, or rating are not the same thing as republishing someone's article or photo.

This actor collects information from public pages. It does not log in and it does not bypass access controls.

For a longer explanation, see Apify's article [Is web scraping legal?](https://blog.apify.com/is-web-scraping-legal/).

# Actor input Schema

## `mode` (type: `string`):

What to scrape.

## `where` (type: `string`):

SoQL $where clause, e.g. value > '1000'

## `q` (type: `string`):

Full-text search ($q) across text columns

## `orderBy` (type: `string`):

SoQL $order (stable paging needs a unique order)

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

Stop after this many successful rows. Hard max is 1000.

## `requestDelaySecs` (type: `number`):

Seconds to wait between requests.

## `userAgent` (type: `string`):

User-Agent header sent with each request.

## `timeoutSecs` (type: `integer`):

Overall run budget in seconds.

## `requestTimeoutSecs` (type: `integer`):

Per-request timeout in seconds.

## `proxyConfiguration` (type: `object`):

Optional proxy. Leave off unless you need it.

## Actor input object example

```json
{
  "mode": "rows",
  "where": "",
  "q": "",
  "orderBy": ":id",
  "maxItems": 100,
  "requestDelaySecs": 1,
  "userAgent": "ActorResearch/1.0",
  "timeoutSecs": 300,
  "requestTimeoutSecs": 30,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

Dataset rows in the overview table.

## `dataset` (type: `string`):

Full dataset for this run.

## `items` (type: `string`):

Dataset items as JSON.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("bigibyte/dallas-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("bigibyte/dallas-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 '{}' |
apify call bigibyte/dallas-building-permits-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bigibyte/dallas-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/M0Zlq1Od9VAjZbsGN/builds/kpXqAhrH6j87eWcMO/openapi.json