# Texas Contractor License Lookup & Leads (TDLR) (`quarrylane-data/texas-tdlr-contractor-license-leads`) Actor

Texas TDLR contractor license lookup and leads from the official open-data file: HVAC (A/C), electrical, elevator, sign and appliance contractors with phone, address, status and expiry. Filter by trade, city, ZIP or county.

- **URL**: https://apify.com/quarrylane-data/texas-tdlr-contractor-license-leads.md
- **Developed by:** [Quarrylane Data](https://apify.com/quarrylane-data) (community)
- **Categories:** Lead generation, Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.50 / 1,000 contractor licence records

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

## Texas TDLR Contractor License Leads

Export **Texas contractor licences from the official Texas Department of Licensing and Regulation (TDLR) open-data file** on data.texas.gov. Get each licensed contractor's **business name, licence number and type, trade, status, expiration date, business phone, address and county** as clean JSON, CSV or Excel. Filter by **trade**, **city**, **county**, **ZIP** or **business name**. Turn on **monitor mode** to get only newly listed contractors.

This is the Texas-only spoke of Quarrylane's [US Contractor License Leads](https://apify.com/quarrylane-data/us-contractor-license-leads) bundle — built for buyers searching for a **Texas contractor license** scraper or TDLR licence lookup.

### What does this Actor do?

TDLR publishes one statewide "All Licenses" file. This Actor reads that official SODA API, keeps **contractor** licence types (**A/C, electrical, elevator, electrical sign and appliance-installation contractors**, about 36,000 records), and returns **one normalized record per licence**. No login, no browser, no unofficial scrape of the TDLR search form.

Texas does **not** issue a statewide general-building or roofing contractor licence through TDLR. Those trades are licensed locally or by other boards. Use this Actor for the official TDLR contractor categories above.

### Who uses it?

- **HVAC, electrical, elevator, sign and appliance suppliers** building a Texas contractor list
- **Insurers and surety desks** checking who is currently licensed
- **Lead agencies and Clay/n8n users** who want a daily TDLR new-licence watch

### Input

| Field | What it does |
|---|---|
| `trades` / `licenseTypeKeywords` | Optional trade or licence-type filter (HVAC, electrical, elevator, sign, appliance). Leave empty for all TDLR contractor types. |
| `cities`, `counties`, `zipCodes` | Geography filters. Counties use TDLR names such as `HARRIS` or `TRAVIS`. |
| `businessNameContains` | Look up one company. |
| `activeOnly` | Default on. Skips licences whose official expiration date has passed. |
| `requirePhone` | Keep only records with a published business telephone. |
| `onlyNew` + `monitorName` | Monitor mode: pay only for licences not seen under this key before. The first run is billed as standard records and seeds the rest of the current file without charging. |
| `enrichWebsiteContacts` | Optional. The official TDLR file has no website field, so this is a no-op unless a website is already on the record. Domains are never guessed. |
| `maxItems` | Default 50 (auto-test safe). Free plans are capped at 15. Paid plans can go up to 100,000. |

#### Example input

```json
{
  "licenseTypeKeywords": ["electrical"],
  "cities": ["Houston"],
  "activeOnly": true,
  "requirePhone": true,
  "maxItems": 50
}
```

### Output

Each record includes `businessName`, `principalName`, `licenseNumber`, `licenseType`, `status`, `isActive`, `expirationDate`, `phone`, `address`, `city`, `state`, `zip`, `county`, `source`, `sourceAgency`, `verifyAt` (the official TDLR licence search) and `sourceDataUrl`. Enrichment fields are present when you turn that option on.

Sample from a real run of this Actor (person-name and personal contact fields masked in this README only; long text and lists shortened):

```json
{
  "recordId": "TX:100",
  "businessName": "OBY'S APPLIANCE INSTALLATION, INC",
  "dbaName": null,
  "principalName": null,
  "businessEntityType": null,
  "licenseNumber": "100",
  "licenseType": "Appliance Installation Contractor",
  "licenseTypeCode": "RAIC",
  "licenseClass": null,
  "specialties": [],
  "trades": [],
  "status": "Active",
  "isActive": true,
  "firstLicensedDate": null,
  "issueDate": null,
  "expirationDate": "2027-02-28",
  "phone": "+15124540550",
  "phoneFormatted": "(512) 454-0550",
  "address": "8705 DAWNRIDGE CIRCLE",
  "address2": null,
  "city": "AUSTIN",
  "state": "TX",
  "zip": "78757",
  "county": "TRAVIS",
  "bondCompany": null,
  "bondAmount": null,
  "insuranceCompany": null,
  "insuranceAmount": null,
  "insuranceExpirationDate": null,
  "website": null,
  "websiteEmails": null,
  "websitePhones": null,
  "websiteSocials": null,
  "contactsEnriched": false,
  "stateBusinessId": null,
  "extra": {
    "mailingAddress": "PO BOX 9277",
    "mailingCityStateZip": "AUSTIN TX 78766-9277",
    "mailingCounty": "TRAVIS",
    "continuingEducationFlag": "N"
  },
  "licensingState": "TX",
  "source": "TX",
  "sourceName": "Texas TDLR contractor licenses (A/C, electrical, elevator, sign, appliance)",
  "sourceAgency": "Texas Department of Licensing and Regulation",
  "verifyAt": "https://www.tdlr.texas.gov/LicenseSearch/",
  "sourceDataUrl": "https://data.texas.gov/d/7358-krk7",
  "scrapedAt": "2026-11-13T04:26:31.087Z"
}
```

### Pricing

Pay per result, with no monthly rental:

| Event | Price |
|---|---|
| Contractor licence record (`contractor-record`) | **$5.00 per 1,000 records** |
| New-licence lead (`new-license-lead`, later monitor-mode runs) | **$25.00 per 1,000 records** |
| Website contact enrichment (`contact-enriched`) | **$20.00 per 1,000 successful enrichments**, only when an email or phone is found |

The official file has no issue date. Monitor mode is the supported way to watch for newly listed contractors. Set **Max cost per run** if you want a hard budget. Free Apify plans are capped at 15 results per run.

#### Price per event and Store discounts

| Event | Charged for | Free plan | Bronze | Silver | Gold | Per 1,000 (Free plan) |
|---|---|---|---|---|---|---|
| Contractor licence record (`contractor-record`) | Charged for each Texas TDLR contractor licence saved to your dataset in a standard run, including the first run of a new-licence monitor. | $0.005 | $0.0045 | $0.004 | $0.0035 | $5.00 |
| New-licence lead (`new-license-lead`) | Charged instead of the standard record for each licence delivered on a later run when monitor mode (onlyNew) is on and this monitor name has already been used. | $0.025 | $0.0225 | $0.02 | $0.0175 | $25.00 |
| Website contact enrichment (`contact-enriched`) | Charged in addition to the licence record when enrichWebsiteContacts is on and an email or phone is extracted from the firm's own website. Not charged for social links only, and never charged when the record has no website. | $0.02 | $0.018 | $0.016 | $0.014 | $20.00 |

Prices are in USD per event. This Actor is pay-per-event only: there is no monthly rental and no separate platform usage charge on top, because compute is included in the event price. Apify Bronze, Silver and Gold subscribers get the discounted prices automatically. Set **Max cost per run** in the run options to cap spend, and the Actor stops before it goes over.

### How to automate with Clay.com, n8n, Make, and Claude MCP

All examples use this Actor's Store ID `quarrylane-data/texas-tdlr-contractor-license-leads`. Replace `YOUR_APIFY_TOKEN` with your Apify API token (Console → Settings → API & Integrations). Never paste a token into a public workflow.

#### Official Apify API (run-sync-get-dataset-items)

This endpoint starts a run, waits for it to finish, and returns the dataset items in one call:

```bash
curl -sS -X POST \
  "https://api.apify.com/v2/acts/quarrylane-data~texas-tdlr-contractor-license-leads/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"licenseTypeKeywords":["electrical"],"cities":["Houston"],"maxItems":15}'
```

The same URL works from any HTTP client. Use `~` between the username and Actor name. For a daily new-licence monitor, pass `"onlyNew": true` and a stable `"monitorName"`. The first run is billed as standard records; later runs charge the new-licence event only for IDs you have not already received.

#### n8n

- **Apify node** (community, `n8n-nodes-apify`): add the Apify credentials, choose **Run Actor**, set the Actor to `quarrylane-data/texas-tdlr-contractor-license-leads`, and paste the JSON input above into the Actor input field. Use the node's "wait for finish" option, then read the default dataset.
- **HTTP Request node** (works without the community package): Method `POST`, URL `https://api.apify.com/v2/acts/quarrylane-data~texas-tdlr-contractor-license-leads/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN`, header `Content-Type: application/json`, body as JSON. Each item in the response is one licence.

#### Make (Integromat)

Use the **Apify** module's **Run an Actor** action (or an HTTP module with the endpoint above). Map the input fields you need. After the run finishes, use **Get Dataset Items** on the default dataset, or call `run-sync-get-dataset-items` in a single HTTP module to receive the rows directly.

#### Clay.com

Add an **HTTP API** enrichment column:

- Method: `POST`
- URL: `https://api.apify.com/v2/acts/quarrylane-data~texas-tdlr-contractor-license-leads/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN`
- Headers: `Content-Type: application/json`
- Body: `{"licenseTypeKeywords":["electrical"],"cities":["Houston"],"maxItems":15}`

Map dataset fields (`businessName`, `licenseNumber`, `phone`, `city`, `expirationDate`) into Clay columns. Keep `maxItems` small in table-wide enrichments so each row does not start a large run.

#### Claude and the Apify MCP server

This Actor is MCP-compatible (limited permissions). Point Claude, Cursor, or any MCP client at Apify's hosted server and include this Actor in the `tools` query parameter (that is the official parameter for selecting Actors):

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=quarrylane-data/texas-tdlr-contractor-license-leads"
    }
  }
}
```

On first connect, sign in to Apify (OAuth) or send an `Authorization: Bearer YOUR_APIFY_TOKEN` header. In Claude, you can also add `https://mcp.apify.com?tools=quarrylane-data/texas-tdlr-contractor-license-leads` as a custom connector under Settings → Connectors. Then ask Claude to "list active electrical contractors in Houston from the Texas TDLR Actor."

### Is it legal to use this data?

Yes. The source is TDLR's official public open-data publication on data.texas.gov (dataset 7358-krk7). The Actor reads the official JSON API, honours the portal's crawl delay, and never logs in. Use the data responsibly and follow the CAN-SPAM Act, the TCPA, do-not-call rules and applicable Texas law when you contact businesses.

### FAQ

**Why are general contractors or roofers missing?** TDLR does not issue a statewide general-building or roofing contractor licence. Those lists live at cities and other boards. This Actor covers official TDLR contractor types only.

**Can I also get Washington, Oregon or California contractors?** Yes — use the multi-state bundle [US Contractor License Leads](https://apify.com/quarrylane-data/us-contractor-license-leads), which includes Texas and the other official registries.

**Does monitor mode need an issue date?** No. TDLR does not publish one. The first `onlyNew` run seeds every current matching ID; later runs return only licences that were not in that set.

Built by **Quarrylane Data**. Not affiliated with the Texas Department of Licensing and Regulation. Data comes from the public file at data.texas.gov.

### More US public-record lead data by Quarrylane Data

| Actor | What you get |
|---|---|
| [NYS Contract Reporter Bids & RFPs](https://apify.com/quarrylane-data/nys-contract-reporter-bids-scraper) | New York State government bids, RFPs, RFQs and grants with due dates and links |
| [US Contractor License Leads (9 states)](https://apify.com/quarrylane-data/us-contractor-license-leads) | Official contractor licences from 9 state registries with phone, address and status |
| [MWBE, DBE & Diversity-Certified Business Leads](https://apify.com/quarrylane-data/us-diversity-certified-business-leads) | Officially certified minority, women-owned and disadvantaged businesses |
| [US Federal Contract Awards (USAspending)](https://apify.com/quarrylane-data/usaspending-federal-contract-awards) | Recent federal prime contract awards and the companies that won them |
| [NPPES NPI New Provider Leads](https://apify.com/quarrylane-data/nppes-npi-new-provider-leads) | Newly registered medical practices and providers from the official CMS NPI file |
| [FMCSA New Authority Leads](https://apify.com/quarrylane-data/fmcsa-new-authority-leads) | Newly granted USDOT / MC trucking authorities with carrier census details |
| [EPA Enforcement Case Leads](https://apify.com/quarrylane-data/epa-enforcement-case-leads) | EPA and state environmental enforcement cases with penalties and facilities |
| [OCC Bank Applications Monitor](https://apify.com/quarrylane-data/occ-bank-applications-monitor) | OCC bank charter, branch, merger and control applications |
| [Federal Reserve Bank M\&A Applications](https://apify.com/quarrylane-data/fed-bank-holding-company-applications) | Federal Reserve bank holding company formation, acquisition and merger filings |

# Actor input Schema

## `trades` (type: `array`):

Optional trade filter. Official TDLR contractor types in this file are A/C (HVAC), electrical, elevator, electrical sign and appliance-installation contractors — not general building or roofing licences (those are issued locally or by other boards). Leave empty to return all TDLR contractor types.

## `licenseTypeKeywords` (type: `array`):

Extra free-text match on TDLR licence type, e.g. 'electrical', 'elevator', 'A/C', 'appliance', 'sign'. Combined with Trades using OR.

## `businessNameContains` (type: `string`):

Case-insensitive match on business or owner name (useful for verifying one company).

## `cities` (type: `array`):

Exact city names as they appear in the TDLR file, e.g. 'Houston', 'Dallas', 'Austin', 'San Antonio'.

## `counties` (type: `array`):

Texas county names as published by TDLR, e.g. 'HARRIS', 'DALLAS', 'TRAVIS' (case-insensitive).

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

5-digit ZIPs or prefixes, e.g. '78701' or '787' (Austin area).

## `activeOnly` (type: `boolean`):

Skip expired licences (TDLR publishes an expiration date, not a separate status flag).

## `requirePhone` (type: `boolean`):

Keep only records with a published business telephone number.

## `onlyNew` (type: `boolean`):

Remembers every licence delivered (and, on the first run, every other current match) under the monitor key. Later scheduled runs return and charge only new records. The official TDLR file has no issue date, so this is the way to watch for newly listed contractors.

## `monitorName` (type: `string`):

Label for this saved monitor (plain text, not a password or API key). When "Only new" monitor mode is on, the Actor remembers which records it has already delivered under this name and returns only new ones next time. Use a different name per filter set or client, for example "client-a-weekly". Older inputs that use monitorKey still work.

## `enrichWebsiteContacts` (type: `boolean`):

When a record already includes the firm's own website, fetch the homepage plus likely /contact and /about pages (lightweight HTTP only, robots.txt respected, short timeouts). Adds websiteEmails, websitePhones and websiteSocials. Charges an extra $0.02 contact-enriched event only when an email or phone is found. The official TDLR file does not publish websites, so this is a no-op unless a website is present; domains are never guessed.

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

Upper limit of licences to return (Free Apify plan: 15 per run). The default is a cheap, auto-test-safe sample.

## Actor input object example

```json
{
  "activeOnly": true,
  "requirePhone": false,
  "onlyNew": false,
  "monitorName": "default",
  "enrichWebsiteContacts": false,
  "maxItems": 50
}
```

# Actor output Schema

## `results` (type: `string`):

Texas TDLR contractor licence leads (business name, licence, trade, phone, address and official source links).

# 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("quarrylane-data/texas-tdlr-contractor-license-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("quarrylane-data/texas-tdlr-contractor-license-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 '{}' |
apify call quarrylane-data/texas-tdlr-contractor-license-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,quarrylane-data/texas-tdlr-contractor-license-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/hOuAZnYQVULffJ1is/builds/XuIf6YvF44mJT5aYD/openapi.json
