Safety data
that answers.
OSHIFY turns public workplace injury, illness and fatality records, plus the OSHA and MSHA standards text, into one consistent, queryable API. Ask by industry, event, injury, state or year. Every answer carries its source, dataset year and retrieval date.
Pulled from the API, just now.
These figures load from the public endpoints when the page opens. Nothing here is typed in by hand or computed by a model.
Two kinds of record. Never mixed.
One thing that happened
OSHA severe injury reports: date, state, industry, what the worker was doing, what was injured. Employer names and addresses are not published here.
A published aggregate
BLS fatality counts and hours-based rates by industry. Events are never added up to imitate a statistic.
OIICS + NAICS
Event, nature, body part and source use BLS OIICS codes. Industries use NAICS, keyed by vintage so codes that moved between years never collide.
Plain HTTP. Keys optional.
GET only, typed endpoints, JSON back. Try it with no key at 60 requests a minute and 1,000 rows a day per IP. Create a key in the console for 600 requests a minute and the full monthly allowance. An OpenAPI spec and an llms.txt are published for agents.
/events/aggregateCount severe injuries by event, nature, body part, source, year, state or industry.TRY →
GET/eventsList individual reported events with filters. 100 rows per call.TRY →
GET/statistics/cfoiBLS fatalities by industry and event. Add series=rates for hours and fatal injury rates.TRY →
GET/soiiBLS nonfatal injury and illness rates and counts by industry, state, year and case type.TRY →
GET/msha/accidents/aggregateMSHA mine accident counts by year, state, commodity, degree and type.TRY →
GET/severitySeverity proxy for an industry: expected cost per 100 workers and a 1 to 5 index. A labeled estimate.TRY →
GET/standards/searchFull-text search of OSHA 29 CFR 1904, 1910, 1926 and MSHA 30 CFR. Fetch one section at /standards/{section}.TRY →
GET/naics/searchFind NAICS industries and SOC occupations by plain name, with parents, children and typical occupations.TRY →
GET/snapshotsEvery dataset, its source, period, retrieval date and license note.TRY →
SPEC/openapi.jsonOpenAPI description. Also /llms.txt for language models.OPEN →
# Falls, struck-by and caught-in: what hurts construction workers most, since 2020 curl "https://api.oshify.com/events/aggregate?by=event&naics_prefix=23&year_from=2020"
Keys, usage and billing.
Sign in at console.oshify.com to run the API for your team. The first 50,000 rows each month are free. After that it is $0.10 per 1,000 rows returned, paid from a prepaid balance with optional auto top-off.
API keys
Create and revoke keys. Send one as a Bearer token or X-API-KEY header.
Playground and data browser
Run any endpoint from the browser, or explore by industry, state and dataset without writing code.
Logs and usage
Every request is logged for 30 days. See rows, calls and spend by key and by month, and export billing as CSV.
Billing
Add funds by card, turn on auto top-off, and get low-balance warnings before keyed calls stop.
API reference
Every endpoint, parameter and error code in one place.
Numbers you can trace.
- 01Every number carries its source, dataset period and retrieval date.
- 02Reported incidents and published statistics are not a compliance determination. Reporting is incomplete and uneven by source.
- 03Published figures are never invented. Rates shown are the ones BLS publishes. Derived endpoints such as /severity and /model/rates are labeled as estimates.
- 04Data comes from US federal public records. OSHIFY is not affiliated with or endorsed by the Department of Labor, OSHA or BLS.
- 05OSHA enforcement is separate from ISNetworld and Avetta prequalification. They are different things.