ComplyLedge — OSHA compliance data API
Why ComplyLedge
Underwriting-grade OSHA risk data — resolved, corrected, ready to query.
Three problems sit between the raw federal records and a risk number you can underwrite on. We solve all three, so you integrate once and price with confidence.
01 · RESOLVE<br>One business, one stable id
Fuzzy-match a name (and optional address) to a durable establishment_id, then pull the full profile. Store the id once and re-query the same site at every renewal — no re-matching, no drift.
02 · CORRECT<br>Corrected, not just copied
The raw records mislead in three ways we fix before you ever see the record:
Vacated citations excluded — you never price on penalties that were withdrawn on appeal.
Fatalities counted per injury — the accurate grain, ~18% more complete than inspection-level counts.
Federal and state-plan — the ~22 states OSHA doesn't run directly, included, not dropped.
03 · SHIP<br>Key in minutes, not quarters
One clean endpoint, a confidence score on every match, daily freshness, and transparent usage-based pricing. Sign up and get your first response in minutes — self-serve, no procurement cycle.
The call
Resolve, then retrieve.
Two endpoints. The first finds the establishment and scores the match; the second returns its full compliance profile.
1 — Resolve a name to candidates
# GET /v1/osha/establishments/search<br>curl -sG $API/v1/osha/establishments/search \<br>-H "Authorization: Bearer $KEY" \<br>--data-urlencode "name=BP Products North America" \<br>--data-urlencode "state=TX"
Response — ranked candidates, each scored
"query": { "name": "bp products north america", "state": "TX" },<br>"results": [<br>"establishment_id": "est_0a70f12d…", // carry this into call 2<br>"establishment_name": "BP PRODUCTS NORTH AMERICA, INC.",<br>"address": { "city": "TEXAS CITY", "state": "TX" },<br>"inspection_count": 36,<br>"violation_count": 772,<br>"match_confidence": 1.0,<br>"match_type": "exact_name" // … full rollup on every result<br>},<br>"establishment_id": "est_5b31c9a4…",<br>"establishment_name": "BP PIPELINES (NORTH AMERICA) INC.",<br>"address": { "city": "HOUSTON", "state": "TX" },<br>"match_confidence": 0.61, // looser name → threshold it out<br>"match_type": "fuzzy"<br>],<br>"has_more": true,<br>"coverage": "federal_and_state_plan",<br>"data_as_of": "2026-06-30"
2 — Retrieve the full profile by id
curl -s $API/v1/osha/establishments/est_0a70f12d… \<br>-H "Authorization: Bearer $KEY"
Response — the record you price on
"establishment_name": "BP PRODUCTS NORTH AMERICA, INC.",<br>"establishment_id": "est_0a70f12d…", // stable — store it, re-query at renewal<br>"address": { "city": "TEXAS CITY", "state": "TX" },<br>"naics_code": "324110",<br>"jurisdiction": "federal",<br>"inspection_count": 36,<br>"violation_count": 772,<br>"willful_violation_count": 463,<br>"total_penalties_usd": 36169000.0,<br>"fatality_count": 3,<br>"match_confidence": 1.0,<br>"match_type": "exact_name"
Compliance
Business risk data — clean for commercial underwriting.
ComplyLedge serves public U.S. Department of Labor / OSHA records about<br>business establishments — so it's not a "consumer report" under the FCRA ,<br>and it's clean to use for commercial and workers'-comp underwriting . It isn't intended<br>for decisions about individuals (personal lines, employment, or credit). Details in the<br>Terms.
Who's behind this
Built for decisions that carry real weight.
ComplyLedge is built by a technical founder with nine years of infrastructure<br>experience at a FAANG company and a focus on developer-first APIs. That background is<br>what surfaced the gap: data that feeds decisions like workers'-comp and commercial<br>insurance pricing deserves better than a raw government export or a six-figure, sales-led<br>contract with an incumbent risk vendor. ComplyLedge closes that gap — the same rigor,<br>without the DIY build or the enterprise price tag. For product questions, edge cases, or<br>a dataset you need next, you can reach the founder directly.<br>Contact the founder →
Pricing
Simple, usage-based.
Try it free above with no signup, or start a 7-day free trial of Starter — card required,<br>cancel anytime. Your key appears on the next page and is emailed to you. (Launch pricing.)
Starter 7-DAY TRIAL
$29/mo
Monthly API requests: 2,500<br>Rate limit: 25 / min<br>Full establishment profiles<br>Cancel anytime
Start free trial
Pro
$99/mo
Monthly API requests: 25,000<br>Rate limit: 60 / min<br>Email support
Subscribe
Custom
Let's talk
High-volume pricing<br>Multiple datasets (roadmap)<br>Async email support
Contact us
↑ enter your email, then pick a plan
FAQ
Questions, answered.
Where does the data come from?<br>Directly from the U.S. Department of Labor's public OSHA enforcement datasets — the same<br>inspection, violation, and accident records OSHA publishes, covering both federal OSHA and<br>state-plan states.
How fresh is the data?<br>We ingest DOL's enforcement files daily, so the API reflects OSHA's latest published data —<br>typically within a day of DOL publishing. Every response includes a data_as_of date, so you<br>always know...