hyperfeedeventsregulatory-action-api
event_family · regulatory

Regulatory Action API.

FDA approvals and rejections, NHTSA probes, DOJ/FTC enforcement, SEC orders, FAA actions. Every federal regulator action against a public company, as one typed stream.

family_idregulatory
event_types9
trailing 30d emitted342
audited precision98.4%
median latency68s
What this tracks

Every event_type in regulatory.

Each type emits the same envelope with a family-specific payload. Subscribe to the whole family or filter to specific types.

01
fda_approval_granted

FDA grants approval for NDA, BLA, or 510(k) submission.

02
fda_approval_declined

Complete Response Letter issued on drug/device approval.

03
nhtsa_probe_opened

NHTSA opens preliminary evaluation or engineering analysis.

04
doj_enforcement_action

DOJ files civil or criminal enforcement action.

05
ftc_enforcement_action

FTC files complaint, consent order, or merger challenge.

06
sec_enforcement_action

SEC files charges or issues Wells notice.

07
faa_enforcement_action

FAA issues enforcement notice or certificate action.

08
cyber_incident_disclosed

Material cybersecurity incident disclosed per SEC rules.

09
regulatory_settlement_reached

Settlement with monetary penalty or consent decree.

Example event

One real event. Full JSON payload.

This is the exact shape you'd receive via GET /v1/events or via a signed webhook delivery.

Request

GET/v1/events?family=regulatory&regulator=NHTSA&since=2026-04-01
// Query all regulatory events in the last 14 days
GET /v1/events?family=regulatory&regulator=NHTSA&since=2026-04-01
Authorization: Bearer hf_live_...

Response · 200 OK

200 OKapplication/json
{
  "event_id": "evt_20260413_tsla_regulatory",
  "schema_version": "2026-04-20",
  "event_type": "nhtsa_probe_opened",
  "assertion_type": "fact",
  "status": "official_announced",
  "priority": "critical",
  "entity": {
    "ticker": "TSLA",
    "name": "Tesla, Inc."
  },
  "lifecycle": {
    "detected_at": "2026-04-13T13:42:18Z",
    "announced_at": "2026-04-13",
    "effective_at": "2026-04-13",
    "confirmed_at": "2026-04-13"
  },
  "source": {
    "type": "regulator",
    "name": "FDA · NHTSA · DOJ · FTC · SEC · FAA",
    "tier": "tier_1"
  },
  "summary": {
    "one_line": "NHTSA upgraded its Tesla FSD investigation to an engineering analysis covering approximately 3.2 million vehicles."
  },
  "payload": {
    "regulator": "NHTSA",
    "action_type": "probe_upgraded",
    "product_id": "FSD",
    "scope": "3.2M vehicles",
    "docket_number": "EA26-007",
    "consent_decree": false
  },
  "confidence": {
    "overall": 0.98,
    "identity": 0.99,
    "event_classification": 0.98
  }
}
Recent activity · delayed 7d

Recent regulatory events.

Pulled live from the public delayed feed. Click through to the full tape for payloads, lifecycle, and source links.

Apr 13
FDA approval declined · reproxalap
ALDX· Aldeyra
CRITICAL
Apr 13
NHTSA probe upgraded · 3.2M vehicles
TSLA· Tesla
CRITICAL
Apr 12
FAA enforcement · 737 MAX quality
BA· Boeing
CRITICAL
Apr 11
DOJ antitrust verdict · illegal monopoly
GOOGL· Alphabet
CRITICAL
Apr 10
$150M settlement · subscription fees
ADBE· Adobe
HIGH
Apr 09
Cyber incident disclosed · material
UNH· UnitedHealth
CRITICAL
Sources · where this data comes from

Ranked by authority, merged by entity.

Every event carries a source object. When the same event is confirmed by multiple sources, they merge into one canonical event with an evidence array.

Tier 1 · regulator

FDA · NHTSA · DOJ · FTC · SEC · FAA

Direct from agency press rooms and action dockets

Tier 1 · filing

SEC 8-K Item 1.05, 8.01

Material cyber incidents, other events · real-time EDGAR

Tier 1 · court

PACER / federal courts

Civil complaints, consent decrees, verdicts

Tier 1 · trusted news

Reuters · Bloomberg · Law360

Often first to report; marked trusted_report until regulator confirms

Tier 2 · state

State AGs · state regulators

Multi-state AG actions, state insurance commissions

Tier 2 · issuer

Company 8-K responses

Company statements in response to regulator action

Schema · payload fields

Family-specific fields inside payload.

All events share the same envelope (event_id, entity, lifecycle, sources, assertion_type, confidence). The payloadis what's specific to this family.

FieldTypeDescriptionExample
payload.regulatorstringFederal or state agency taking the action."NHTSA"
payload.action_typestringSpecific action taxonomy."probe_upgraded"
payload.product_idstring?Drug name, vehicle model, or product identifier."FSD"
payload.scopestringScope of affected products or operations."3.2M vehicles"
payload.penalty_amountnumber?Monetary penalty in USD, if disclosed.150000000
payload.consent_decreebooleanWhether a consent decree is involved.false
payload.docket_numberstring?Agency docket or case number."PE22-014"
Start tracking

Start tracking regulatory events.

Developer tier from $99/mo. Real-time, webhooks, and 250-entity watchlists at $299 Pro.