Jobs and employers
Open postings with their full text, the employers behind them, and a changes feed that keeps a copy in sync, with dates a backtest can trust.
WARN noticesState records30 states and DC, daily
An employer with 100 or more staff has to give 60 days' notice of a mass layoff or a closure, under the WARN Act, and each state publishes the notices it gets in its own format. pdatum reads them every day and serves them in one shape. Each names the employer, the place, how many people and the dates, and links to the private companies lenders hold.
More than 37,000 notices from 30 states and DC, each state read every day, and every notice kept once read.
$ pdatum warn list -q "acme fabrication" --json \ | jq '.data[0] | {state, employer, workers, notice_at, effective_at, company}' { "state": "tx", "employer": "Acme Fabrication (Plano)", "workers": 112, "notice_at": 1786492800, "effective_at": 1791763200, "company": "acme-fabrication" } # which states are read, and why not the rest $ pdatum warn states # every notice linked to one company $ pdatum warn pull --company acme-fabrication # what is new since yesterday, as JSON lines $ pdatum warn changes --since 1d
Illustrative: Acme and its notice are invented.
The questions the feed is built to answer, and the field that answers each.
A notice links to a company when the employer's name, as the state wrote it, is that company's name. Case, punctuation, a legal form and a site in parentheses are ignored. Nothing else is, and a former name never links.
workers is how many the notice says are affected.
notice_at is when the employer gave notice, and
effective_at when the layoff starts. Each is null when
the state leaves it out, never a guess.
/warn/changes returns every notice read for the first
time since then, and every notice newly linked to a company or
employer. Upsert by id and a copy stays in sync.
/warn/states lists every state and DC and when we
last read each. Asking about a state we do not read yet says so,
never answers with a zero.
One record per notice. The API reference has a whole example.
How the data behaves, in brief. The front page lists every source we read, and the API reference has the rest.
/warn/states lists every state,
when it was last read and where its notices start.Open postings with their full text, the employers behind them, and a changes feed that keeps a copy in sync, with dates a backtest can trust.
The contracts and grants federal agencies have awarded any company you name, from USAspending.gov: how many, how much, from which agencies, and when the work ends.
Every loan a business development company reports each quarter, from its SEC filings, and how every other lender we read marks the same loan.
Every private company the BDCs we read hold, under every name their lenders file it as, with one slug. Any name can be looked up; one we do not hold is searched for on EDGAR.
Franchisors' registrations and exemption notices with the states, every Texas filing back to 1985, with their brands, dates and status, linked to the companies lenders hold.
Every private capital raise a company has reported to the SEC on Form D since 2008: how much it offered, how much it sold and to how many investors, linked to the companies lenders hold.
Keys are issued by hand while the API is young. Write to pdatum@pearachute.com and say what you are building and which data you need. If you need a state we do not read yet, say which: requests decide which comes next.