# Building Permits Dallas TX — Verified CSV, Updated (`data_place/dallas-building-permits-fresh`) Actor

198 rows, built to answer one question: Which Building Permits Dallas TX? Every row includes:

- city

- commercial permits

- council districts

- days since last permit

- distinct work types

- distinct ZIP code codes

- emergency repair permits

- first permit in window

- last permit date

- name

- permi

- **URL**: https://apify.com/data\_place/dallas-building-permits-fresh.md

- **Developed by:** [dataplace](https://apify.com/data_place) (community)

- **Categories:** Lead generation

- **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/platform/actors/running/actors-in-store#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Building Permits Dallas TX — Verified CSV, Updated July 2026

198 rows, built to answer one question: Which Building Permits Dallas TX? Every row includes:

- city
- commercial permits
- council districts
- days since last permit
- distinct work types
- distinct ZIP code codes
- emergency repair permits
- first permit in window
- last permit date
- name
- permits last 60 days
- permits per week
- rank by permit volume
- residential permits
- state
- top job reason
- top work type
- window end
- window start
- ZIP code codes worked

Filter via the Actor input; data refreshed with each new build (check the build date above).

- city
- commercial permits
- council districts
- days since last permit
- distinct work types
- distinct ZIP code codes
- emergency repair permits
- first permit in window
- last permit date
- name
- permits last 60 days
- permits per week
- rank by permit volume
- residential permits
- state
- top job reason
- top work type
- window end
- window start
- ZIP code codes worked

### What one result contains

One result = one record (one JSON object pushed to your dataset).
Every record carries these 22 fields: entity\_id, city, commercial\_permits, council\_districts, days\_since\_last\_permit, distinct\_work\_types, distinct\_zip\_codes, emergency\_repair\_permits, first\_permit\_in\_window, kind, last\_permit\_date, name, permits\_last\_60\_days, permits\_per\_week, rank\_by\_permit\_volume, residential\_permits, state, top\_job\_reason, top\_work\_type, window\_end, window\_start, zip\_codes\_worked.

Example shape:

```json
{
  "entity_id": "...",
  "city": "...",
  "commercial_permits": "...",
  "council_districts": "...",
  "days_since_last_permit": "...",
  "distinct_work_types": "..."
}
```

You are charged once per record returned — no records, no charge.

# Actor input Schema

## `county` (type: `string`):

Only firms in this county (e.g. TRAVIS)

## `zip` (type: `string`):

Only firms at this ZIP

## `min_permits` (type: `integer`):

Only firms with at least this many permits on file

## `limit` (type: `integer`):

Cap the number of records returned

## Actor input object example

```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("data_place/dallas-building-permits-fresh").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("data_place/dallas-building-permits-fresh").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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 data_place/dallas-building-permits-fresh --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=data_place/dallas-building-permits-fresh",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/Ga1JxlHLXVUOGg96g/builds/7tuc3PJoDUtBDnvSm/openapi.json