# Layoff Early Warning — WARN Act Filings, Watchlisted (`alaudinburki/warn-act-layoff-radar`) Actor

Aggregates official state WARN Act mass-layoff filings (60-days'-notice legal filings) — currently CA and TX, both live structured sources — and matches them against your company watchlist, ranked by headcount severity. Recruiters, journalists, and diligence teams check this by hand today.

- **URL**: https://apify.com/alaudinburki/warn-act-layoff-radar.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 results

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

## Layoff Early Warning — WARN Act Filings, Watchlisted

US federal law (the WARN Act) requires employers above a size threshold to
file a public notice **60 days before** a mass layoff or plant closure.
There's no single federal feed for this — every state publishes its own
filings, in its own format, and nobody aggregates them cleanly. Recruiters,
journalists, and PE/VC diligence teams currently check this by hand,
state by state.

This starts with the two states that publish real structured data — **CA**
(a live XLSX report, updated twice weekly) and **TX** (a clean Socrata JSON
API) — matched against a company watchlist, ranked by headcount severity.

### Coverage — honest, not a 50-state promise

Only **CA and TX** have live adapters right now. Most other states require
a public-records request or publish only as unstructured PDF — genuinely
not automatable the way these two are. Built as one adapter per state, so
adding a state later is a contained addition, not a rewrite. Treat a
"clear" result as **"clear in CA/TX,"** not "clear everywhere."

### Input

```json
{ "watchlist": ["Genentech", "JPMorgan Chase"], "states": ["CA", "TX"] }
```

Leave `watchlist` empty to return every current filing instead of matching
against specific companies.

### Sample output

```json
{
  "state": "CA",
  "company": "Genentech, Inc.",
  "county": "San Mateo County",
  "noticeDate": "2026-06-26",
  "effectiveDate": "2026-07-29",
  "layoffType": "Layoff Permanent",
  "employeeCount": 103,
  "severity": "significant",
  "matchedWatchlistEntry": "Genentech",
  "industry": "54 Professional Scientific and Technical Services"
}
```

### Typical uses

- **Recruiter early-warning** — watch specific companies for layoff signals
  before they hit the news.
- **Journalism / research** — track layoff activity across CA and TX
  without checking two separate state government sites by hand.
- **PE/VC diligence** — check a target or portfolio company for recent
  WARN filings before a deal.

### Pricing

**$3.00 / 1,000 results** (`$0.003` per filing).

### ⚠️ Read before you act

- **Coverage is CA + TX only.** This is stated plainly because a "no
  results" answer for a company outside these two states means nothing —
  it wasn't checked, not confirmed clean.
- **Company matching is word-boundary, not substring** — "Chase" won't
  false-positive-match every company with "purchase" in an address field;
  "JPMorgan Chase" requires both words present.
- **Re-run periodically.** New filings post continuously (CA updates twice
  weekly); this is a point-in-time snapshot.

### FAQ

- **Why only CA and TX?** They're the two states that publish genuinely
  structured, live data (an XLSX report and a Socrata JSON API,
  respectively) rather than requiring a public-records request or only
  offering unstructured PDFs.
- **What does `severity` mean?** A headcount-based tier (`major` ≥500,
  `significant` ≥100, `notable` ≥25, `small` below) — the buyer's real
  question is "how big a deal is this," not just "did it happen."
- **Can more states be added?** Yes — the adapter pattern is designed for
  it. It's a matter of finding each state's actual data source, which
  varies widely in quality and format.

### Related actors

- **OT/ICS Advisory Matcher** — the same official-feed-matched-against-
  your-list pattern, for security advisories instead of layoff filings.
- **SEC EDGAR Filings** — another public, legally-required-disclosure
  actor, for material corporate events.

# Actor input Schema

## `watchlist` (type: `array`):

Company names to watch for in new WARN Act filings, e.g. Genentech, JPMorgan Chase. Leave empty to return every current filing instead of matching a watchlist.

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

Which states to check. Currently CA and TX have live structured data sources; other states publish only as records requests or unstructured PDFs and are not yet covered.

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

Hard cap on items returned. You are never charged beyond this.

## Actor input object example

```json
{
  "states": [
    "CA",
    "TX"
  ],
  "maxItems": 1000
}
```

# Actor output Schema

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

WARN Act filings, ranked by headcount severity.

## `qualityReport` (type: `string`):

States checked, severity breakdown, coverage note, and problems.

# 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("alaudinburki/warn-act-layoff-radar").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("alaudinburki/warn-act-layoff-radar").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 alaudinburki/warn-act-layoff-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alaudinburki/warn-act-layoff-radar"
        }
    }
}
```

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/c2llItoFgX5pTn2a5/builds/pBDU3G5hGvCLvaaPv/openapi.json