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.
Franchise filingsState recordsTexas and Florida
Before a franchisor sells franchises in some states, it files there: a registration, or a notice that it is exempt. pdatum reads those filings and serves them in one shape: every one the Texas Secretary of State lists, and every franchisor Florida lists with where its filing stands. Each names the franchisor, its brands and the names it gave up, and links to the private companies lenders hold.
More than 16,000 Texas filings back to 1985, and more than 2,700 Florida franchisors, read every week.
$ pdatum franchises list -q "acme tutoring" --json \ | jq '.data[0] | {name, status, filed_at, company, matched}' { "name": "ACME TUTORING FRANCHISE LLC", "status": "exempt", "filed_at": 1753142400, "company": "acme-tutoring", "matched": "ACME TUTORING" } # which states are read, and why not the rest $ pdatum franchises states # every filing linked to one company $ pdatum franchises pull --company acme-tutoring
Illustrative: Acme and its filing are invented.
The questions the feed is built to answer, and the field that answers each.
A filing links to a company we track when one of its legal or brand names is that company's name. A franchisor often files under a subsidiary named for its brand, so a link someone reviewed says what it rests on instead.
The state writes every name in one field. names splits
it: the franchisor's legal name, its brands
(trade), and the names it used to have
(former), which never link.
filed_at is when it registered or filed its exemption.
status says where the filing stands in words every state
shares, and state_status in the state's own, which can say
why a franchisor stopped.
/franchises/states lists every state and DC, and why we
do not read the ones we do not. Asking only about a state we do not
read is refused with the reason, never answered with a zero.
One record per filing. The API reference has a whole example.
id is what identifies a
filing.registration or an exemption; and
registered, exempt, expired or
terminated, beside the status in the state's own words
where it gives them.How the data behaves, in brief. The front page lists every source we read, and the API reference has the rest.
/franchises/states lists every state and when each was
last read.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.
The layoff and closure notices states publish under the WARN Act, read every day and served in one shape: the employer, the place, how many people and when, 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.