# US WARN Layoff Notices + Company Watchlist (`canarywhistle/warn-layoff-notices`) Actor

WARN Act layoff notices from 47 US states and DC since 2005, the layoffs filed but not yet effective, every amendment a state makes, and a watchlist check for your own list of companies.

- **URL**: https://apify.com/canarywhistle/warn-layoff-notices.md
- **Developed by:** [CanaryWhistle](https://apify.com/canarywhistle) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 notice rows

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

## US WARN Layoff Notices + Company Watchlist

WARN Act layoff notices from **47 US states and Washington, DC**, back to 2005, refreshed every six hours from each state's own published register. About 39,000 notices covering 4.4 million workers.

Four ways to run it:

| Mode | What you get |
|---|---|
| **Watchlist** | Paste your own list of companies (suppliers, portfolio holdings, sales accounts). For each one: every WARN notice on record in every state, workers affected, notices filed but not yet effective, the next effective date, and other distress signals we hold. |
| **Recent** | Notices filed in the last N days, filtered by state, size and industry. |
| **Upcoming** | Layoffs that have been filed but have not happened yet, by effective date, up to a year ahead. |
| **Changes** | Every new notice, and every notice a state has since amended (effective date moved, headcount changed, layoff reclassified as a closure), since N days ago. |

### Why the watchlist mode exists

Most people asking "is anyone on my list laying people off?" have the list already. Searching 48 state websites one name at a time is the slow part, and the same employer is filed under different names: "Walmart", "Wal-Mart Associates, Inc." and "Walmart #1258" are one company here. The watchlist mode does the matching across every state at once and returns one row per name you sent, including the names with nothing on record, so you can see what was checked.

Alongside WARN notices, a watchlist row includes other public distress signals where we hold them: SEC 8-K filings that report restructuring or exit costs, PBGC pension plan terminations, and large federal contracts approaching their end date.

### Example output (Upcoming mode)

```json
{
  "mode": "upcoming",
  "company": "Example Manufacturing Co.",
  "state": "OH",
  "city": "Dayton",
  "employees": 142,
  "industry": "Manufacturing",
  "type": "Closure",
  "notice_date": "2026-10-09",
  "effective_date": "2026-12-11",
  "url": "https://canarywhistle.com/company/example-manufacturing-co"
}
```

Notice rows in Recent and Changes mode also carry `source_url` (the state page the notice was published on), `roles`, and `revisions_url` (the notice's full as-filed history).

### Input

- **What to fetch**: watchlist, recent, upcoming or changes.
- **Companies**: one per line, watchlist mode only. Up to 1,000 a run.
- **Days**: how far back for recent and changes, how far ahead for upcoming. 1 to 365.
- **States**: two-letter codes. Empty means all.
- **Minimum employees affected**: skip smaller notices.
- **Industry**: healthcare, hospitality, manufacturing, logistics, finance, technology, retail and a few others. Most notices name no industry, so empty is usually right.
- **Maximum results**: stop after this many rows.

### Pricing

Pay per result. A notice row (recent, upcoming, changes) is one *record* event. A watchlist row is one *company-checked* event, because it summarizes everything on record for that employer. Set a spending limit on the run and the Actor stops cleanly when it is reached.

### Scheduling

Run Changes mode daily with Days set to 1 to get only what is new or amended since yesterday. Run Watchlist weekly against your supplier list to catch a notice before its effective date.

### What WARN data is and is not

The federal WARN Act requires employers with 100 or more employees to give 60 days' notice of a plant closing or mass layoff, and several states set lower thresholds. So this is the set of layoffs large enough to trigger a notice and filed with a state. It is not every US layoff. States publish on their own schedules, some only post a rolling recent window, and three (New Hampshire, Oklahoma and Wyoming) do not publish usable notices at all. A notice is a statement of intent: dates move and some layoffs are reduced or withdrawn, which is why the Changes mode exists.

### Source

Data from [CanaryWhistle](https://canarywhistle.com), which collects and normalizes every state WARN register. Full methodology at [canarywhistle.com/methods](https://canarywhistle.com/methods). For signed webhooks and higher volume, see the [CanaryWhistle API](https://canarywhistle.com/developers).

# Actor input Schema

## `mode` (type: `string`):

watchlist: check your own list of companies. recent: notices filed in the last N days. upcoming: layoffs filed but not yet effective. changes: every new and amended notice since N days ago.

## `companies` (type: `array`):

One company per line: suppliers, portfolio holdings, accounts. Legal-entity variants and store numbers are matched to one employer. Up to 1,000.

## `days` (type: `integer`):

recent and changes: how far back. upcoming: how far ahead.

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

Two-letter codes, e.g. CA, TX. Leave empty for all.

## `minEmployees` (type: `integer`):

Skip notices smaller than this.

## `industry` (type: `string`):

Optional: healthcare, hospitality, manufacturing, logistics, finance, technology or retail. Most notices name no industry, so leaving this empty is usually right.

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

Stop after this many results.

## Actor input object example

```json
{
  "mode": "recent",
  "companies": [
    "Walmart",
    "Intel",
    "Boeing"
  ],
  "days": 30,
  "minEmployees": 0,
  "maxItems": 1000
}
```

# 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 = {
    "companies": [
        "Walmart",
        "Intel",
        "Boeing"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("canarywhistle/warn-layoff-notices").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 = { "companies": [
        "Walmart",
        "Intel",
        "Boeing",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("canarywhistle/warn-layoff-notices").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 '{
  "companies": [
    "Walmart",
    "Intel",
    "Boeing"
  ]
}' |
apify call canarywhistle/warn-layoff-notices --silent --output-dataset

```

## MCP server setup

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

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/Aw89BN0rNSFYFrCHm/builds/IuEJlfMpOFYo6g1MG/openapi.json