# TX & OR Contractor License Leads — Electrical, Plumbing, HVAC (`seemuapps/contractor-license-leads-tx-or`) Actor

Export licensed electrical, plumbing, and HVAC contractor leads from Texas and Oregon state licensing boards with business name, contact, address, and license status.

- **URL**: https://apify.com/seemuapps/contractor-license-leads-tx-or.md
- **Developed by:** [Andrew](https://apify.com/seemuapps) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 lead exporteds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

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

## TX & OR Contractor License Leads — Electrical, Plumbing, HVAC

Export licensed electrical, plumbing, and HVAC contractor leads from Texas and Oregon state licensing boards — business name, license status, address, phone, and county for every match.

### What you get

- Business name, license number, license type, and live Active/Expired status
- Street address, city, county, and ZIP for every licensed contractor
- Phone number where the state publishes one (Texas TDLR includes it; Oregon BCD does not)
- Sourced directly from the Texas Department of Licensing and Regulation (TDLR) and Oregon Building Codes Division (BCD) public open-data feeds — updated as the states update their registries
- Paginated output: each run returns a cursor so you can pull the full registry across multiple runs

### Use cases

- Outbound lead generation for suppliers, insurers, and SaaS tools selling to trade contractors
- Territory and market-sizing research — count active electrical/plumbing/HVAC contractors by county
- Competitive mapping — find every licensed electrician or plumber in a target city
- Compliance and vetting — confirm a contractor's license is active before hiring

### How to use

1. Choose **States**: `TX`, `OR`, or both
2. Choose **Trade**: All available trades, Electrical, Plumbing, or HVAC / A-C
   - Texas TDLR does not license plumbers — Texas is skipped automatically if you pick Plumbing
   - Oregon BCD has no distinct HVAC/A-C category — Oregon is skipped automatically if you pick HVAC
3. Optionally filter by **County** (both states) or **City** (Oregon only)
4. Set **Max Items** (default 500; set 0 for unlimited — the run paginates until every selected state is exhausted or the run times out)
5. Run the actor — leads appear in the **Dataset** tab

### Resuming a large pull

After the run finishes, open the **Key-value store** tab → copy the `NEXT_PAGE_ID` value → paste it into **Page ID** on your next run. If `NEXT_PAGE_ID` is `null`, you've fetched everything for your selected states/trade/filters.

### Output format

Each dataset record:

```json
{
  "state": "TX",
  "trade": "electrical",
  "licenseType": "Electrical Contractor",
  "licenseNumber": "17001",
  "licenseStatus": "Active",
  "licenseExpirationDate": "2026-08-31",
  "businessName": "ELECTRICAL INNOVATIONS OF TEXAS",
  "contactName": "ELECTRICAL INNOVATIONS OF TEXAS",
  "streetAddress": "2923 DEDMAN",
  "city": "PASADENA",
  "addressState": "TX",
  "zipCode": "77503",
  "county": "HARRIS",
  "phone": "2815426301",
  "sourceAgency": "Texas Department of Licensing and Regulation (TDLR)"
}
```

Results are scoped to business-level (contractor) license types — not individual practitioner licenses like Journeyman/Apprentice Electrician, which the source registries do not associate with a business address or phone.

# Actor input Schema

## `states` (type: `array`):

Which state licensing boards to pull from. TX = Texas TDLR (electrical, HVAC/A-C). OR = Oregon BCD (electrical, plumbing). Plumbing is not licensed by TDLR in Texas; HVAC is not a distinct category in Oregon's BCD data.

## `trade` (type: `string`):

Which trade to filter licenses to. 'All' pulls every trade available for each selected state.

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

Only return leads whose licensed county contains this text, e.g. 'Harris'. Leave empty for the whole state.

## `city` (type: `string`):

Only return Oregon leads in this exact city, e.g. 'Portland'. Texas does not publish a separate city field to filter on server-side.

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

Drop expired or inactive licenses from the results.

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

Maximum number of leads to return in this run. Set 0 for unlimited (the run paginates until every selected state is exhausted or the run times out).

## `pageId` (type: `string`):

Paste NEXT\_PAGE\_ID from the previous run's Key-value store to resume where it left off.

## Actor input object example

```json
{
  "states": [
    "TX",
    "OR"
  ],
  "trade": "all",
  "activeOnly": true,
  "maxItems": 500
}
```

# Actor output Schema

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

One contractor license per record. Fields: state, trade, licenseType, licenseNumber, licenseStatus, licenseExpirationDate, businessName, contactName, streetAddress, city, addressState, zipCode, county, phone, sourceAgency.

## `nextPageId` (type: `string`):

NEXT\_PAGE\_ID record in the default key-value store. Paste into Page ID on the next run to resume; null when the selected states are exhausted.

# 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("seemuapps/contractor-license-leads-tx-or").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("seemuapps/contractor-license-leads-tx-or").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 seemuapps/contractor-license-leads-tx-or --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,seemuapps/contractor-license-leads-tx-or"
        }
    }
}

```

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/MGHDBaaGpfjtA4myB/builds/Z1dDvDTS9seATNTcE/openapi.json