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.
Capital raisesSEC Form DSince 2008
A company that sells shares or notes privately files a Form D with the SEC within 15 days of its first sale. pdatum reads every one an operating company has filed since 2008, from the SEC's Form D data sets and EDGAR's daily filings, and serves them in one shape. Each says how much was offered, how much was sold and to how many investors, and links to the private companies lenders hold.
360,000 raises by 186,000 companies since 2008, and a few hundred more every business day.
$ pdatum raises list -q "acme robotics" --json \ | jq '.data[0] | {name, filed_at, sold, investors, company}' { "name": "Acme Robotics, Inc.", "filed_at": 1790726400, "sold": 42000000, "investors": 17, "company": "acme-robotics" } # this year's biotech raises of $50 million or more $ pdatum raises pull --industry biotechnology \ --filed-since 2026-01-01 --min-sold 50000000 # every raise linked to one company $ pdatum raises pull --company acme-robotics
Illustrative: Acme and its raise are invented.
The questions the feed is built to answer, and the field that answers each.
A raise links to a company we track when the issuer's name is that
company's name. filed_at is when it told the SEC, and
first_sale_at when the first investor bought in.
sold against offered, and how many
investors. An amendment updates them, and every filing of
one offering shares its offering number.
The SEC's cik, the issuer's address, where it is
incorporated, and the names it says it used before, so two companies of
one name can be told apart.
/raises/changes sends every raise read, changed or
linked since a time you give, and every answer says how far the
filings run in read_through.
One record per filing. The API reference has a whole example.
D) or an amendment (D/A) and which filing it
amends, and the offering every filing of it shares.region, and
country everywhere else.How the data behaves, in brief. The front page lists every source we read, and the API reference has the rest.
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.
The registrations and exemption notices franchisors file with the states: the franchisor, its brands, its dates and status, 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.