# License Verification — Multi-State (Contractor & Professional) (`querymill/license-verification-multi-state`) Actor

Verify contractor and professional licenses against official state board sources (CA CSLB, TX TDLR, WA L\&I, CT eLicensing, DE Professional Regulation, NYC DCWP) and get one normalized record per lookup: holder, status, issue/expiration dates, board, and source.

- **URL**: https://apify.com/querymill/license-verification-multi-state.md
- **Developed by:** [Eric Trammell](https://apify.com/querymill) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$40.00 / 1,000 license verifications

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

## License Verification — Multi-State (Contractor & Professional)

Verify a contractor or professional license against the **official state board source** and get back one clean, normalized record — the same schema whether the license is from California, Texas, Washington, Connecticut, Delaware, or New York City.

### Supported sources

| State | Board | Source type |
|---|---|---|
| CA | Contractors State License Board (CSLB) | Official license-check portal |
| TX | Dept. of Licensing and Regulation (TDLR) — all programs | Official open-data API |
| WA | Dept. of Labor & Industries (contractors) | Official open-data API |
| CT | Dept. of Consumer Protection (eLicensing) | Official open-data API |
| DE | Division of Professional Regulation | Official open-data API |
| NY | NYC Dept. of Consumer and Worker Protection | Official open-data API (NYC-issued licenses only — not NY State) |

### Input

```json
{
  "queries": [
    { "state": "CA", "licenseNumber": "1155602" },
    { "state": "TX", "licenseNumber": "2716", "licenseType": "A/C Technician" },
    { "state": "WA", "licenseNumber": "ECOSTSC758NN" }
  ]
}
```

- `state` (required): two-letter code.
- `licenseNumber` (required): exact license number as issued by the board. CT also accepts the full credential code (e.g. `HIC.0631057`).
- `licenseType` (optional): disambiguates numbers that repeat across programs — mainly TX (numbers repeat across TDLR programs) and CT (numbers repeat across credential types).

### Output

One record per query:

```json
{
  "state": "CA",
  "board": "California Contractors State License Board (CSLB)",
  "licenseNumber": "1155602",
  "licenseType": "B - GENERAL BUILDING",
  "holderName": "AMERICAN RELIABLE CONSTRUCTION & REMODELING",
  "status": "active",
  "statusRaw": "This license is current and active. ...",
  "issueDate": "2026-05-21",
  "expirationDate": "2028-05-31",
  "city": "LOS ANGELES",
  "zip": "91430",
  "found": true,
  "sourceUrl": "https://www.cslb.ca.gov/OnlineServices/CheckLicenseII/LicenseDetail.aspx?LicNum=1155602",
  "checkedAt": "2026-10-23T01:28:11.578Z",
  "extras": { "bondAmount": 25000, "entity": "Corporation" }
}
```

- `status` is normalized to `active` / `expired` / `inactive` / `not_found`; the board's own wording is always preserved in `statusRaw`.
- TX note: the TDLR dataset publishes no status field, so TX status is derived from the expiration date and flagged in `extras.statusSource`.
- Every record carries an `extras` object with board-specific detail (bond amount and surety for CA/WA, classifications, workers-comp status, disciplinary flags where published).

### Reliability

Each state is an isolated module with its own fixture-backed smoke test (`ops/smoke-test.js`) that runs known licenses against the live sources and fails loudly if a portal changes shape — so a broken source is a one-file patch, never a silent bad answer.

### Pricing model (when monetized)

Pay-per-event: one `verification` event per lookup that finds a record; misses are free. All lookups are plain HTTP (no browser automation), so platform compute per run stays minimal.

### Pricing

Pay per event: **$0.04 per successful verification** (a lookup that finds a record). Lookups that find no record are free.

# Actor input Schema

## `queries` (type: `array`):

One entry per license to verify. state: two-letter code (CA, CT, DE, NY, TX, WA — NY covers NYC-issued licenses only). licenseType is optional and only needed where numbers repeat across programs (notably TX and CT).

## Actor input object example

```json
{
  "queries": [
    {
      "licenseNumber": "1155602",
      "state": "CA"
    },
    {
      "licenseNumber": "ECOSTSC758NN",
      "state": "WA"
    }
  ]
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `items` (type: `string`):

No description

## `itemCount` (type: `string`):

No description

# 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 = {
    "queries": [
        {
            "licenseNumber": "1155602",
            "state": "CA"
        },
        {
            "licenseNumber": "2716",
            "licenseType": "A/C Technician",
            "state": "TX"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("querymill/license-verification-multi-state").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 = { "queries": [
        {
            "licenseNumber": "1155602",
            "state": "CA",
        },
        {
            "licenseNumber": "2716",
            "licenseType": "A/C Technician",
            "state": "TX",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("querymill/license-verification-multi-state").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 '{
  "queries": [
    {
      "licenseNumber": "1155602",
      "state": "CA"
    },
    {
      "licenseNumber": "2716",
      "licenseType": "A/C Technician",
      "state": "TX"
    }
  ]
}' |
apify call querymill/license-verification-multi-state --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,querymill/license-verification-multi-state"
        }
    }
}
```

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/h24faC7vmGI3Xi84M/builds/PaNs0PRaxkrLgTaxb/openapi.json