# Fort Worth Development Permits Scraper (`zerobreak/fort-worth-development-permits-scraper`) Actor

Fort Worth Development Permits Scraper is a Python tool to extract permit numbers, issue dates, project descriptions, addresses, and valuation estimates from city databases. It exports structured construction datasets into clean CSV or JSON formats

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

## Pricing

from $2.99 / 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

### Fort Worth Development Permits Scraper — Construction and Development Permit Records

![Fort Worth Development Permits Scraper cover](https://images.bigibyte.com/cdn-cgi/image/width=1260,height=540,fit=cover,format=webp/apify-actors-covers/fort-worth-development-permits-scraper-cover.png)

Collect public development permit records from the City of Fort Worth, Texas, in a structured dataset. Retrieve permit numbers, project types, property addresses, filing dates, current statuses, owner names, and job values for real estate research, contractor lead generation, and local market analysis.

### Overview

This actor collects records from the City of Fort Worth's public Development Permits dataset. It supports keyword searches, custom SQL-style filters, and newest-first collection.

The collected information can help researchers, contractors, developers, and analysts explore development activity across Fort Worth.

### Features

- Collect Fort Worth development permit records.
- Search permits using keywords.
- Filter records using custom conditions.
- Retrieve the latest permits first.
- Sort records using custom ordering.
- Set a maximum number of records to collect.
- Export results in JSON, CSV, Excel, and other supported Apify dataset formats.
- Store collected records in an Apify dataset.

### Collection Modes

| Mode | Description |
|---|---|
| `search` | Searches permit records using text across supported fields, including permit numbers, addresses, types, owners, work descriptions, and statuses. |
| `filter` | Collects records matching a custom SQL-style condition. |
| `latest` | Collects the newest permit records first, normally ordered by filing date. |

### Input Parameters

| Parameter | Description |
|---|---|
| `mode` | Selects the collection mode: `search`, `filter`, or `latest`. |
| `searchText` | Keyword or phrase used to search permit records in search mode. |
| `where` | Optional SQL-style filter condition used in filter mode. |
| `maxItems` | Maximum number of records to collect. |
| `orderBy` | Field and sorting direction used to order the results. |
| `requestDelaySecs` | Delay between collection requests. |

### Example Input

**Collect the latest development permits**

```json id="fw001"
{
  "mode": "latest",
  "maxItems": 50,
  "orderBy": "File_Date DESC",
  "requestDelaySecs": 1
}
```

**Search permits by keyword**

```json id="fw002"
{
  "mode": "search",
  "searchText": "GROVE",
  "maxItems": 25,
  "requestDelaySecs": 1
}
```

**Filter issued permits**

```json id="fw003"
{
  "mode": "filter",
  "where": "Current_Status = 'Issued'",
  "maxItems": 25,
  "requestDelaySecs": 1
}
```

### What Data Does This Actor Extract?

The actor collects available development permit fields, including:

| Field | Description |
|---|---|
| `unique_key` | Unique identifier for the permit record. |
| `permit_number` | Development permit number. |
| `permit_type` | Main permit type. |
| `permit_subtype` | More specific permit classification. |
| `permit_category` | Permit category. |
| `special_text` | Additional project or work information. |
| `address` | Property or project address. |
| `owner_full_name` | Owner name recorded in the dataset. |
| `file_date` | Date the permit application was filed. |
| `current_status` | Current status recorded in the dataset. |
| `job_value` | Reported job or project value. |
| `use_type` | Property or project use classification. |
| `object_id` | Source record identifier. |
| `scraped_at` | Date and time the record was collected. |

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

### Example Output

```json id="fw004"
{
  "unique_key": "PB26-143553151344366049964840",
  "permit_number": "PB26-14355",
  "permit_type": "Commercial Accessory Structure",
  "permit_subtype": "Remodel",
  "permit_category": "NA",
  "special_text": "876471-TMO EQUIP. UPGRADE",
  "address": "2420 CHESTNUT AVE",
  "owner_full_name": "RODRIGUEZ, BLAS",
  "file_date": "2026-10-23T00:00:00.987000+00:00",
  "current_status": "Pending",
  "job_value": "25000.0",
  "use_type": "Other",
  "object_id": "1620626",
  "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 development permit records.

You can:

- Export records as JSON, CSV, or Excel.
- Filter permits by status, type, or subtype.
- Analyze reported job values.
- Group permits by filing date or project category.
- Review contractor-related and property ownership information where available.
- Use the collected data in real estate research and reporting workflows.

### Use Cases

- **Construction Lead Generation:** Discover development and construction permit records.
- **Contractor Research:** Explore permit types, project descriptions, and associated activity.
- **Real Estate Research:** Identify areas with recorded development activity.
- **Property Research:** Analyze permit addresses, owner information, and project classifications.
- **Market Analysis:** Study permit filing trends and reported project values.
- **Development Tracking:** Review permit statuses and filing dates.

### FAQ

**Who can use this actor?**

Researchers, analysts, real estate professionals, contractors, developers, and other users interested in Fort Worth development permits.

**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.

**How do I get the newest permits?**

Use `latest` mode with `orderBy` set to `File_Date DESC`.

**Can I search for permits at a specific location or with a particular status?**

Yes. Use `search` mode for keywords or `filter` mode with an appropriate condition in the `where` parameter.

### Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, sponsored by, or otherwise officially associated with the City of Fort Worth. 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 fetch from the Fort Worth permits FeatureServer.

## `searchText` (type: `string`):

Text matched across permit number, address, type, owner, work description, and status (search mode).

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

ArcGIS SQL where clause, e.g. Current_Status = 'Issued'

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

ArcGIS orderByFields, e.g. File_Date DESC or ObjectId ASC

## `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": "latest",
  "searchText": "GROVE",
  "where": "Current_Status = 'Issued'",
  "orderBy": "File_Date DESC",
  "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("zerobreak/fort-worth-development-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("zerobreak/fort-worth-development-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 zerobreak/fort-worth-development-permits-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zerobreak/fort-worth-development-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/S8h2XASR37Co34HdJ/builds/hOSZVPOTBd3jsf3Yx/openapi.json