# Contractor License Watch: Oregon CCB + Washington L\&I (`implementable_antler/contractor-license-watch`) Actor

Paste OR CCB / WA L\&I license numbers; get status, days to license/bond/insurance expiry, an at-risk flag, and what changed since your last run. Official open data.

- **URL**: https://apify.com/implementable_antler/contractor-license-watch.md
- **Developed by:** [Blake Runckel](https://apify.com/implementable_antler) (community)
- **Categories:** Business, Real estate, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 contractor checkeds

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

## Contractor License Watch: Oregon CCB + Washington L\&I

Paste a watchlist of Oregon CCB and Washington L\&I contractor license numbers. Each run returns, per contractor: license status, days until the license, bond and insurance expire, an `atRisk` flag, and **what changed since your last run** (carrier switch, bond change, status change, new expiry date).

### Input

| Field | Description |
|---|---|
| `licenseNumbers` | OR CCB numbers (digits) and/or WA L\&I numbers. Prefix `OR:` / `WA:` to force a state. |
| `atRiskDays` | Window for the at-risk flag (default 30). `atRisk` is true when status is not ACTIVE, or any expiry is lapsed or within the window. |
| `watchlistName` | Name of the key-value store in your account that keeps your last snapshot (`LAST_SNAPSHOT`). Use different names for different watchlists. |

### Output fields

`state, licenseNumber, found, status, businessName, licenseType, licenseExpires, daysToLicenseExpiry, bondCompany, bondAmount, bondExpires, daysToBondExpiry, insuranceCarrierOnFile, insuranceAmount, insuranceExpires, daysToInsuranceExpiry, atRisk, atRiskReasons, changesSinceLastRun, firstSeenThisWatchlist, checkedAt, source`

`changesSinceLastRun` is `null` on the first run of a watchlist, then a list of `{field, old, new}`.

`recentChanges` (Oregon only) lists field changes `{changedAt, licenseType, field, old, new}` recorded by our daily snapshots of the CCB feed in the last `recentChangeDays` days, so the first run already shows recent carrier switches, lapses and renewals. `recentChangesCoverage` gives the snapshot date range; changes before it are not covered. The change history is refreshed by an automated daily rebuild of this Actor. Every row carries `historyCoverageEnd` (last snapshot date). If that date is more than 3 days before the check date, `historyStale` is true and `historyWarning` explains that recent changes after that date are not shown. Dates in `recentChanges` are ISO (YYYY-MM-DD).

`noInsuranceOnFile` is true when an Oregon license has no insurance carrier on file in the feed; it counts toward `atRisk`.

### Important limits — read before relying on this

- **Insurance shown is the carrier on file with the state, not a certificate of insurance and not proof of coverage.** Ask the contractor for a current COI.
- **Washington bond and insurance: not published.** The WA L\&I open-data feed (data.wa.gov `m8qx-ubtq`) does not publish bond or insurance fields. For WA rows, `bondCompany`, `bondAmount`, `bondExpires`, `insuranceCarrierOnFile`, `insuranceAmount`, `insuranceExpires` and their day counts are always `null`. They are never inferred.
- **Oregon status: not published.** The Oregon feed (data.oregon.gov `g77e-6bhs`, "CCB Active Licenses") has no status field, and no other official Oregon open-data API publishes CCB status, so `status` is `null` for Oregon rows. It does **not** confirm a license is active, suspended or inactive; check the CCB lookup. `listedInActiveFeed` only tells you whether the number appears in that feed. A number that isn't listed counts as at-risk.
- Person names are not output: WA `primaryprincipalname` and Oregon `rmi_name` are dropped. Business names appear as published.

### Pricing

Pay per event: one charge per contractor checked.

### Sources and terms

Oregon CCB via data.oregon.gov (Public Domain U.S. Government); WA L\&I via data.wa.gov (ODC Public Domain Dedication). Official Socrata APIs only; no lookup pages are scraped. Freshness equals each publisher's update schedule. No warranty. Do not use the data to contact individuals in violation of TCPA, CAN-SPAM or do-not-call rules.

# Actor input Schema

## `licenseNumbers` (type: `array`):

Oregon CCB numbers (digits) or WA L\&I numbers (e.g. ECOSTSC758NN). Prefix OR: or WA: to force a state.

## `atRiskDays` (type: `integer`):

Flag when license, bond or insurance expires within this many days.

## `watchlistName` (type: `string`):

Named key-value store holding your last snapshot, so changes are diffed per watchlist.

## `includeRecentChanges` (type: `boolean`):

Adds recentChanges: field changes Ledger's daily CCB snapshots recorded for each Oregon license, so you see changes even on your first run.

## `recentChangeDays` (type: `integer`):

How far back recentChanges looks.

## Actor input object example

```json
{
  "licenseNumbers": [
    "231883",
    "ECOSTSC758NN"
  ],
  "atRiskDays": 30,
  "watchlistName": "contractor-license-watch",
  "includeRecentChanges": true,
  "recentChangeDays": 30
}
```

# Actor output Schema

## `results` (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 = {
    "licenseNumbers": [
        "231883",
        "ECOSTSC758NN"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("implementable_antler/contractor-license-watch").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 = { "licenseNumbers": [
        "231883",
        "ECOSTSC758NN",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("implementable_antler/contractor-license-watch").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 '{
  "licenseNumbers": [
    "231883",
    "ECOSTSC758NN"
  ]
}' |
apify call implementable_antler/contractor-license-watch --silent --output-dataset

```

## MCP server setup

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

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/jwQnNx3djT7OXDcam/builds/cAdbJnufXepNySxK3/openapi.json