# Contractor License Lookup (Texas & Florida) (`webworks-tools/contractor-license-lookup`) Actor

Search official Texas TDLR and Florida DBPR contractor license records by name, city, license number or type. Returns license status, type, expiration, and location.

- **URL**: https://apify.com/webworks-tools/contractor-license-lookup.md
- **Developed by:** [Matthew Spindler](https://apify.com/webworks-tools) (community)
- **Features:** Limited permissions
- **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/actors/running/actors-in-store.md#pay-per-usage

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

## Contractor License Lookup — Texas (TDLR) & Florida (DBPR)

Look up contractor licenses from **official state public-record sources** and get clean, structured rows: license number, type, holder name, business name, address, county, expiration date, and status where the state publishes it.

### Use it for

- Verifying a contractor's license before hiring or subcontracting
- Building lead lists of licensed HVAC, electrical, roofing, building and general contractors by county or city
- Checking for expiring licenses (compliance, insurance and supplier teams)

### Data sources (official, public)

| State | Source | Method |
|---|---|---|
| TX | Texas Department of Licensing & Regulation "All Licenses" dataset on data.texas.gov (`7358-krk7`) | Official Socrata open-data API |
| FL | FL DBPR Construction Industry Licensing Board public extract (`CONSTRUCTIONLICENSE_1.csv`), linked from the DBPR "Public Records" page | Official bulk download, streamed and filtered |

**Not included (yet):**

- **Michigan (LARA):** the public lookup is an Accela portal that relies on interactive sessions and postbacks. We found no official API or bulk file, so we left it out instead of scraping it.
- **Ohio (eLicense):** the verification site serves a bot-protection challenge to automated requests, so we didn't build around it.

### Input

- `states`: `["TX","FL"]`
- `nameContains`: part of the business or owner name
- `licenseNumber`: exact license number (TX number, or FL full number such as `CBC006261`)
- `city`: FL exact city; TX substring match on the address. Many TX contractor records have no address, so use `county` instead.
- `county`: TX county name (e.g. `TRAVIS`); FL DBPR county code (e.g. `52`)
- `licenseTypes`: TX names (`A/C Contractor`, `Electrical Contractor`, …), or FL class codes (`CGC` general, `CBC` building, `CRC` residential, `CCC` roofing, `CAC`/`CMC` A/C, `CPC` pool)
- `maxResults`

### Output example

```json
{"state":"TX","licenseNumber":"20025","licenseType":"A/C Contractor","businessName":"DAVID BURGOS","ownerName":"BURGOS, DAVID","county":"TRAVIS","expirationDate":"05/17/2027"}
```

### Notes and limits

- Fields depend on what each state publishes. TX often omits address and phone for individual contractors, and FL doesn't include phone numbers.
- The FL column mapping is inferred from the unlabeled extract, so treat `status` (`C` = Current) as provisional.
- Data is only as current as each state's published file. Always confirm critical checks on the state's own site.
- Use the data lawfully. If you contact anyone from these lists, you must follow CAN-SPAM, TCPA and do-not-call rules.

### Pricing

Pay per result: **$2.50 per 1,000 results** ($0.0025 per license row). No start fee. You only pay for rows returned.

# Actor input Schema

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

TX and/or FL

## `nameContains` (type: `string`):

Business or owner name fragment

## `licenseNumber` (type: `string`):

License number.

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

Exact city name (FL) or prefix (TX)

## `licenseTypes` (type: `array`):

TX e.g. 'A/C Contractor', 'Electrical Contractor'. FL class codes e.g. CGC, CBC, CRC, CCC, CAC, CPC

## `maxResults` (type: `integer`):

Max results.

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

TX: county name (e.g. TRAVIS). FL: DBPR county code (e.g. 52)

## Actor input object example

```json
{
  "states": [
    "TX",
    "FL"
  ],
  "maxResults": 100
}
```

# Actor output Schema

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

All matching license records as a dataset table.

# 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 = {
    "states": [
        "TX",
        "FL"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("webworks-tools/contractor-license-lookup").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 = { "states": [
        "TX",
        "FL",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("webworks-tools/contractor-license-lookup").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 '{
  "states": [
    "TX",
    "FL"
  ]
}' |
apify call webworks-tools/contractor-license-lookup --silent --output-dataset

```

## MCP server setup

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

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/4HcjeyTpApFsE4BKM/builds/9CVW7PdlCZjha0Qpu/openapi.json