📚 OSHA Safety Search — establishment inspection records

Search the official OSHA inspection register (osha.gov/ords/imis) for an establishment's safety/inspection record: inspection type, scope, NAICS, site and the official detail link. Built for due diligence on a contractor or supplier's OSHA history.

Output is one safety_record row per result; billing is pay-per-event, the value event being one resolved safety record (a $0.02 start fee per run, then $0.02 per resolved safety record). Source: www.osha.gov.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Real rows from run j4typ4cm7DW96f47h on build 0.1.10 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

resolved	establishment_site	naics	detail_url	unavailable_reason	input
True	th St Redmond, WA 98052	551114/ Corporate, Subsidiary, and Regional Managing Offices	https://www.osha.gov/ords/imis/establishment.inspection_detail?id=1908		1908104.015
False				ambiguous_refusal_with_candidates	Amazon

The run finished with the status message: PARTIAL: 1 resolved (1 ambiguous refusals, 0 unavailable) of 2 | safety-record billable=1 | safety-record charged=1

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_type (string) — e.g. safety_record
• activity_id (string/null) — e.g. 1908104.015
• resolved (boolean/null) — e.g. True
• establishment_site (string/null) — e.g. th St Redmond, WA 98052
• naics (string/null) — e.g. 551114/ Corporate, Subsidiary, and Regional Managing Offices
• inspection_type (string/null) — e.g. Complaint
• scope (string/null) — e.g. Partial
• union_status (string/null) — e.g. NonUnion
• detail_url (string/null) — e.g. https://www.osha.gov/ords/imis/establishment.inspection_detail?id=1908104.015
• source (string/null) — e.g. https://www.osha.gov/ords/imis/establishment.inspection_detail
• unavailable_reason (string/null) — e.g. ambiguous_refusal_with_candidates
• input (string/null) — e.g. 1908104.015
• found (boolean/null) — e.g. True
• establishment_query (string/null) — e.g. Amazon
• state (string/null) — null in every sample row
• match_count (integer/null) — e.g. 20
• candidates (array/null) — e.g. [{"activity_id": "1916743.015", "date_opened": "09/14/2026", "state": "IN", "ins
• refusal (string/null) — e.g. 'Amazon' is ambiguous: 20 OSHA inspections match. This is a refusal, not an answ
• date_opened (string/null) — null in every sample row
• note (string/null) — null in every sample row

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "establishments": [
    "1908104.015",
    "Amazon"
  ]
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 1 × $0.02 safety-record = $0.04 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
  "establishments": [
    "1908104.015",
    "Amazon"
  ]
}

A bounded run for checking the field shape before scheduling.

3. A full-size run

{
  "establishments": [
    "1908104.015",
    "Amazon"
  ]
}

The same input run on a schedule; each run is billed only for what it delivers.

🧾 JSON sample record

One real record from run j4typ4cm7DW96f47h, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_type": "safety_record",
  "activity_id": "1908104.015",
  "resolved": true,
  "establishment_site": "th St Redmond, WA 98052",
  "naics": "551114/ Corporate, Subsidiary, and Regional Managing Offices",
  "inspection_type": "Complaint",
  "scope": "Partial",
  "union_status": "NonUnion",
  "detail_url": "https://www.osha.gov/ords/imis/establishment.inspection_detail?id=1908104.015",
  "source": "https://www.osha.gov/ords/imis/establishment.inspection_detail",
  "unavailable_reason": null,
  "input": "1908104.015",
  "found": true
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent. Pacing: RATE_PER_SEC=1.5.

Charging. Each resolved safety record is charged at the moment it is pushed (safety-record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

Refusal-with-candidates (by design)

An ambiguous establishment name (many matching inspections) is never resolved to a guessed match and billed. Instead the actor returns a refusal-with-candidates — a notice listing the matching inspections (activity id, date, state, type) — and charges nothing. Pass a specific inspection/activity id from the candidates to resolve one. A query that resolves to a single inspection, or a sourced "no inspection found", is a completed safety-record and is charged. A source outage charges nothing; a run that resolves nothing fails loud.

Source & pacing

The official OSHA establishment inspection register, read anonymously (no key). Paced at 1.5 requests/second with a contact User-Agent; a run is bounded to 50 queries.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Resolved safety record (safety-record)	$0.02	$0.02	$0.02	$0.01

Worked at the live Free-tier price:

• 2 resolved safety records: $0.02 start + 2 × $0.02 = $0.06
• 25 resolved safety records: $0.02 start + 25 × $0.02 = $0.52
• 100 resolved safety records: $0.02 start + 100 × $0.02 = $2.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: PARTIAL: 1 resolved (1 ambiguous refusals, 0 unavailable) of 2 | safety-record billable=1 | safety-record charged=1.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by www.osha.gov. It collects only what the source publishes to any visitor, identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (www.osha.gov) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other public records lookups actors?
A: Same output shape and billing model; this one covers www.osha.gov. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source (RATE_PER_SEC=1.5); there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Fewer rows than expected → the source had fewer items in scope → widen the input.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• UK Legislation Section Retrieval — legislation.gov.uk — UK Legislation Section Retrieval — legislation.gov.uk
• US Federal Register Rule Event Watch — Rules, proposed rules and notices as they publish in the Federal Register
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.