Dallas TX Building Permit Records & Contractor Lookup

Search City of Dallas building permit filings by type, land use, ZIP code, contractor, date range, or declared value and area, or look up exact permits by permit number.

Open in Apify Store$0.99 / 1K on Free

Short answer

Dallas TX Building Permit Records & Contractor Lookup is an Apify Store Actor that returns 14 published output fields, including permitNumber, permitType, activity, status. It lists $0.99 per 1,000 results on the Free plan (pay per event), $0.49 on the Business plan. It takes 27 input settings; one is required (mode). Last updated Nov 20, 2026.

From the public Store listing and published build schema, synced 2026-11-20.
Real estateLead generationAutomation

What it returns

14 fields from the published dataset schema. Export as JSON, CSV or Excel, or read the dataset through the Apify API.

  • permitNumber
  • permitType
  • activity
  • status
  • issuedDate
  • createdDate
  • streetAddress
  • zipCode
  • councilDistrict
  • units
  • value
  • workDescription
  • dataSource
  • sourceUrl

Input

Input settings for Dallas TX Building Permit Records & Contractor Lookup
SettingTypeRequiredDefaultWhat it does
mode string Yes search Which Dallas permit source and lookup path to use.
permitType string No – Filter live permits to one exact type (mode=search). The list covers all 167 types in the current dataset, including the newer Accela-era names. Use 'Any permit type' to skip this filter.
permitTypeCustom string No – Free-text contains-match on the live permit type (mode=search). Takes precedence over 'Permit type (live permits)' when set. Example: 'Solar'.
landUse string No – Filter live permits to one exact land-use classification (mode=search). The list covers all 194 non-empty values currently in the dataset. Use 'Any land use' to skip this filter.
landUseCustom string No – Free-text contains-match on the live land use (mode=search). Takes precedence over 'Land use (live permits)' when set. Example: 'HOSPITAL'.
zipCode string No – Restrict results to one Dallas-area ZIP code. Works in both live and historical modes.
workDescriptionKeyword string No – Only include permits whose work description contains this text (case-insensitive), e.g. 'swimming pool', 'water heater', 'roof'. Works in both live and historical modes.
streetAddressKeyword string No – Only include permits whose street address contains this text (case-insensitive), e.g. 'MAIN ST', 'ELM'. Works in both live and historical modes.
contractorKeyword string No – Only include live permits whose contractor field contains this text (case-insensitive), e.g. a contractor company name. Historical GIS records do not publish contractor names.
mapscoKeyword string No – Only include live permits whose Dallas Mapsco grid reference contains this text (case-insensitive), e.g. '54-B'. There are 3,000+ distinct values, so this is contains-match only.
Show the other 17 settings
More input settings for Dallas TX Building Permit Records & Contractor Lookup
SettingTypeRequiredDefaultWhat it does
hasContractor boolean No false Skip live permits whose contractor field is blank or the owner-builder placeholder. Useful for contractor lead lists. Historical records never carry contractor data.
issuedDateFrom string No – Only include permits issued on or after this date. Live data covers 2018 to today; historical data covers 1971-02-01 through 2024-11-12.
issuedDateTo string No – Only include permits issued on or before this date. Live data covers 2018 to today; historical data covers 1971-02-01 through 2024-11-12.
minValue integer No – Drop permits with a declared value lower than this. Works in both live and historical modes.
maxValue integer No – Drop permits with a declared value higher than this. Works in both live and historical modes.
minArea integer No – Drop permits with a declared area smaller than this. Works in both live and historical modes.
maxArea integer No – Drop permits with a declared area larger than this. Works in both live and historical modes.
sortBy string No default Ordering for mode=search. Historical mode uses 'Historical sort by' instead.
historicalPermitType string No – Filter historical permits (mode=historicalPermits) to one of the City's 35 permit types. Historical records use the coarse pre-Accela type code, not the longer live permit-type labels.
historicalActivity string No – Filter historical permits by activity, such as new construction, alteration, renovation, addition, reconstruction, or finish out.
historicalStatus string No – Filter historical permits by the status recorded when the City extracted the layer in November 2024. Some statuses occur only on unissued applications; those records are returned without an issuedDate.
historicalCategory string No – Filter historical permits by the City's project category.
councilDistrict string No – Filter historical permits to one Dallas City Council district (1-14).
historicalLandUseKeyword string No – Contains-match on the historical land-use description. The layer has 600+ detailed values, so a free-text match is more practical than a dropdown. Example: 'RESTAURANT'.
historicalSortBy string No issuedDateNewestFirst Ordering for mode=historicalPermits.
permitNumbers array No [] Exact Dallas permit numbers to look up, e.g. '2003133024', '2411126010', or 'RES-PLM-26-002314'. Live records are checked first; historical GIS records fill any missing permit and merge extra fields when both sources have it.
maxItems integer No 50 Hard cap on emitted records per run (maximum 10,000). To collect more, split by smaller date ranges, permit types, or council districts and combine the datasets.

Example input

Built from the input form's published example values and defaults.

{
  "mode": "search",
  "permitType": "Building (BU) Single Family  New Construction",
  "hasContractor": false,
  "sortBy": "default",
  "historicalSortBy": "issuedDateNewestFirst",
  "permitNumbers": [],
  "maxItems": 50
}

Run it from code or an AI agent

The same run through the Apify API, with the example input. You need an Apify API token; the run is billed to your account at the Store price.

Python

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run_input = {
    "mode": "search",
    "permitType": "Building (BU) Single Family  New Construction",
    "hasContractor": False,
    "sortBy": "default",
    "historicalSortBy": "issuedDateNewestFirst",
    "permitNumbers": [],
    "maxItems": 50
}

run = client.actor("nimbryxo-studio/dallas-tx-building-permit-records-and-contractor").call(run_input=run_input)
if run is None:
    raise RuntimeError("The Actor run was not found.")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

pip install apify-client

JavaScript

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: "<YOUR_APIFY_TOKEN>" });
const input = {
    "mode": "search",
    "permitType": "Building (BU) Single Family  New Construction",
    "hasContractor": false,
    "sortBy": "default",
    "historicalSortBy": "issuedDateNewestFirst",
    "permitNumbers": [],
    "maxItems": 50
};

const run = await client.actor("nimbryxo-studio/dallas-tx-building-permit-records-and-contractor").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

npm install apify-client

cURL

curl -X POST "https://api.apify.com/v2/actors/nimbryxo-studio~dallas-tx-building-permit-records-and-contractor/run-sync-get-dataset-items"   -H "Authorization: Bearer $APIFY_TOKEN"   -H "Content-Type: application/json"   -d '{"mode":"search","permitType":"Building (BU) Single Family  New Construction","hasContractor":false,"sortBy":"default","historicalSortBy":"issuedDateNewestFirst","permitNumbers":[],"maxItems":50}'

Waits for the run and returns the dataset items (runs over 300 seconds return HTTP 408; start an async run instead).

MCP (AI agents)

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=nimbryxo-studio/dallas-tx-building-permit-records-and-contractor",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

Adds this Actor as a tool in an MCP client that takes a remote server URL (Cursor, VS Code, Claude Code) through Apify's hosted MCP server. OAuth sign-in also works without the header. Clients that only start local servers can wrap the URL with npx mcp-remote.

What a run costs

The result rate falls on higher Apify plans. Each figure is the published per-result rate times the number of results.

Cost of Dallas TX Building Permit Records & Contractor Lookup results by Apify plan
Apify planPer 1,00010,000 results100,000 results
Free plan$0.99$9.90$99
Starter plan$0.82$8.20$82
Scale plan$0.66$6.60$66
Business plan$0.49$4.90$49
  • Every run also has a start event, charged per GB of memory (minimum one): $0.10 on Free, $0.03 on Business. At its default memory of 4 GB a run starts at $0.40 on Free. Fewer, larger runs keep this small.
  • The Free plan includes $5 of monthly usage (Apify pricing, checked 2026-11-11); at the Free rate that covers at most about 5,050 results, less start events and platform usage.
  • Worked example: 10,000 results in one run on the Free plan cost $10.30 ($9.90 for results + $0.40 start), plus Apify platform usage (compute), billed separately by Apify.
  • Pay per event. Platform usage (compute) is billed by Apify on top of the event prices. Compare other tools in the cost estimator.

What people use it for

  • Find building permits
  • Research contractor activity

LA Building Permit Records & Contractor Lookup

Search City of Los Angeles building permits by type, status, office, zip code, valuation, or issue date, or look up exact permits by permit…

12 output fields $0.99 per 1K

TDLR Occupational License Records for Texas Trades

Search Texas TDLR license records across 80+ trades by holder/business name or license number, with trade category, county, and active/expired…

11 output fields $0.99 per 1K

Apartments.com Rental Listing & Floor Plan Scraper

Search Apartments.com rentals by city, bedroom count, price, property type, pet policy, and amenities, or scrape specific listing URLs directly.…

15 output fields $0.99 per 1K

Brazil Rental & Sale Listings by City (QuintoAndar)

Search Brazilian rental and sale property listings by city and transaction type: price breakdown, bedrooms, bathrooms, area, furnishing, and…

9 output fields $0.99 per 1K

Brazilian CNPJ Bulk Lookup & Partner Records Scraper

Look up any number of Brazilian CNPJ numbers and get official Receita Federal data: company name, legal status, CNAE industry codes, address,…

11 output fields $0.99 per 1K

Century 21 Listings & Property Detail Finder

Find Century 21 homes for sale or rent by city, county, neighborhood, or ZIP with price and size filters, or look up a property by address with…

15 output fields $0.99 per 1K

Questions people ask

How much does Dallas TX Building Permit Records & Contractor Lookup cost?

The published result rate depends on your Apify plan: $0.99 per 1,000 on Free, $0.82 per 1,000 on Starter, $0.66 per 1,000 on Scale, $0.49 per 1,000 on Business. So 10,000 results cost about $9.90 on the Free plan and $4.90 on Business, plus a start fee of $0.10 per run per GB of memory on Free. Platform usage is billed separately.

What data does Dallas TX Building Permit Records & Contractor Lookup return?

Its published output schema lists 14 fields: permitNumber, permitType, activity, status, issuedDate, createdDate, streetAddress, zipCode, councilDistrict, units, value, workDescription, and 2 more. A listed field is not guaranteed to be filled in every row.

What input does Dallas TX Building Permit Records & Contractor Lookup need?

Required: mode. Optional settings include permitType, permitTypeCustom, landUse, landUseCustom, zipCode, workDescriptionKeyword.

How do I run Dallas TX Building Permit Records & Contractor Lookup from Python or the API?

Use the Apify API client: in Python, ApifyClient(token).actor("nimbryxo-studio/dallas-tx-building-permit-records-and-contractor").call(run_input=...), then read the run's default dataset (run.default_dataset_id); in JavaScript the same call is client.actor("nimbryxo-studio/dallas-tx-building-permit-records-and-contractor").call(input). Without a client, POST the input JSON to https://api.apify.com/v2/actors/nimbryxo-studio~dallas-tx-building-permit-records-and-contractor/run-sync-get-dataset-items with your API token. Ready-to-paste code with the example input is on this page.

Sources

Actor updated 2026-11-20 Data synced 2026-11-20
Cite this page

Scraper Finder. "Dallas TX Building Permit Records & Contractor Lookup." https://scraperfinder.com/catalogue/dallas-tx-building-permit-records-and-contractor/ (data checked 2026-11-20).

Run Dallas TX Building Permit Records & Contractor Lookup

$0.99 per 1,000 results. Paste the example input above, set your target query, then export the dataset.

Open in Apify Store