NHTSA Vehicle Recall Watch Scraper

Use this actor to monitor public NHTSA recall and vehicle complaint metadata for fleet, product, and safety-operations review. Input VINs, makes, models, manufacturers, or watch terms; get source-linked digest rows for recalls and complaint trends. Complaint records are consumer-submitted and unverified; this actor does not confirm defects or replace official safety review.

Store Quickstart

Run this actor with your target input. Results appear in the Apify Dataset and can be piped to webhooks for real-time delivery. Use dryRun to validate before committing to a schedule.

Key Features

• 🏛️ Government-sourced — Pulls directly from official agency feeds — no third-party aggregators
• ⏱️ Timely digests — Daily/weekly rollups of new filings, rulings, or actions
• 🔍 Keyword watchlists — Flag items matching your compliance/legal watch terms
• 📊 Structured metadata — Agency, date, docket, document type, link — all dataset-ready
• 📡 Webhook alerts — Push to legal/compliance teams the moment new items match watchlist

Use Cases

Who	Why
Developers	Automate recurring data fetches without building custom scrapers
Data teams	Pipe structured output into analytics warehouses
Ops teams	Monitor changes via webhook alerts
Product managers	Track competitor/market signals without engineering time

Input

Field	Type	Default	Description
feeds	array	—	One digest row per watched vehicle, VIN, or manufacturer feed.
recallLookbackDays	integer	30	Default recall lookback window used when a feed-specific override is not set.
complaintLookbackDays	integer	90	Default complaint lookback window used when a feed-specific override is not set.
maxRecallsPerVehicle	integer	50	Default cap on recall evidence rows per feed.
maxComplaintsPerVehicle	integer	100	Default cap on complaint evidence rows per feed.
maxDiscoveredModelsPerFeed	integer	12	Default cap on manufacturer model expansion before complaints and recalls are fetched.
maxEvidenceItems	integer	10	Upper bound on recall or complaint items retained in each digest section.
complaintAlertThreshold	integer	3	Complaint-count threshold that escalates a digest to action_needed.

Input Example

{
  "recallLookbackDays": 30,
  "complaintLookbackDays": 90,
  "maxRecallsPerVehicle": 50,
  "maxComplaintsPerVehicle": 100,
  "maxDiscoveredModelsPerFeed": 12,
  "maxEvidenceItems": 10,
  "complaintAlertThreshold": 3,
  "delivery": "dataset",
  "datasetMode": "all",
  "snapshotKey": "nhtsa-vehicle-recall-digest-state",
  "notifyOnNoNew": true,
  "requestTimeoutSeconds": 30,
  "batchDelayMs": 600,
  "dryRun": false
}

Input Examples

Example: Single-target audit

{
  "targets": [
    "example-target-1"
  ],
  "maxResultsPerTarget": 30
}

Example: Bulk portfolio

{
  "targets": [
    "target-1",
    "target-2",
    "target-3"
  ],
  "maxResultsPerTarget": 50,
  "snapshotKey": "nhtsa-vehicle-recall-digest-state"
}

Example: Recurring delta watch

{
  "targets": [
    "target-1"
  ],
  "snapshotKey": "nhtsa-vehicle-recall-digest-state",
  "emitChangedOnly": true
}

Output

Field	Type	Description
meta	object
errors	array
digests	array
digests[].feedId	string
digests[].feedName	string
digests[].feedType	string
digests[].checkedAt	timestamp
digests[].recallWindowStart	timestamp
digests[].complaintWindowStart	timestamp
digests[].recallLookbackDays	number
digests[].complaintLookbackDays	number
digests[].status	string
digests[].changedSinceLastRun	boolean
digests[].changeSummary	string
digests[].actionNeeded	boolean
digests[].requestedTarget	object
digests[].resolvedCoverage	object
digests[].newRecallCount	number
digests[].totalRecallCount	number
digests[].newComplaintCount	number
digests[].totalComplaintCount	number
digests[].seriousComplaintCount	number
digests[].newSeriousComplaintCount	number
digests[].linkedInvestigationCount	number
digests[].newLinkedInvestigationCount	number
digests[].componentHotspots	array
digests[].investigationSignal	string
digests[].recommendedAction	string
digests[].signalTags	array
digests[].newRecalls	array
digests[].newComplaints	array
digests[].linkedInvestigations	array
digests[].evidence	object
digests[].warnings	array
digests[].error	null

Output Example

{
  "meta": {
    "generatedAt": "2026-04-06T00:00:00.000Z",
    "now": "2026-04-06T00:00:00.000Z",
    "feedCount": 1,
    "totalRecallsFound": 1,
    "newRecallsFound": 1,
    "totalComplaintsFound": 4,
    "newComplaintsFound": 2,
    "actionNeededCount": 1,
    "changedFeedCount": 1,
    "errorCount": 0,
    "snapshot": {
      "key": "nhtsa-f150-quickstart",
      "loadedFrom": "local",
      "savedTo": "local"
    },
    "warnings": [],
    "executiveSummary": {
      "overallStatus": "action_needed",
      "brief": "1 new recall(s); 2 new complaint(s); 1 feed(s) require review.",
      "actionItems": [
        "2021 Ford F-150: Review 1 new recall campaign(s) for 2021 Ford F-150. 1 linked NHTSA action number(s) are in scope."
      ],
      "feedStatuses": [
        {
          "feedId": "ford-f150-2021",
          "feedName": "2021 Ford F-150",
          "status": "new_recalls",
          "newRecallCount": 1,
          "newComplaintCount": 2,
          "actionNeeded": true
        }
      ]
    },
    "delivery": {
      "mode": "dataset",
      "status": "pending"
    }
  },

API Usage

Run this actor programmatically using the Apify API. Replace YOUR_API_TOKEN with your token from Apify Console → Settings → Integrations.

cURL

curl -X POST "https://api.apify.com/v2/acts/taroyamada~nhtsa-vehicle-recall-digest/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "recallLookbackDays": 30, "complaintLookbackDays": 90, "maxRecallsPerVehicle": 50, "maxComplaintsPerVehicle": 100, "maxDiscoveredModelsPerFeed": 12, "maxEvidenceItems": 10, "complaintAlertThreshold": 3, "delivery": "dataset", "datasetMode": "all", "snapshotKey": "nhtsa-vehicle-recall-digest-state", "notifyOnNoNew": true, "requestTimeoutSeconds": 30, "batchDelayMs": 600, "dryRun": false }'

Python

from apify_client import ApifyClient

client = ApifyClient("YOUR_API_TOKEN")
run = client.actor("taroyamada/nhtsa-vehicle-recall-digest").call(run_input={
  "recallLookbackDays": 30,
  "complaintLookbackDays": 90,
  "maxRecallsPerVehicle": 50,
  "maxComplaintsPerVehicle": 100,
  "maxDiscoveredModelsPerFeed": 12,
  "maxEvidenceItems": 10,
  "complaintAlertThreshold": 3,
  "delivery": "dataset",
  "datasetMode": "all",
  "snapshotKey": "nhtsa-vehicle-recall-digest-state",
  "notifyOnNoNew": true,
  "requestTimeoutSeconds": 30,
  "batchDelayMs": 600,
  "dryRun": false
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript / Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_API_TOKEN' });
const run = await client.actor('taroyamada/nhtsa-vehicle-recall-digest').call({
  "recallLookbackDays": 30,
  "complaintLookbackDays": 90,
  "maxRecallsPerVehicle": 50,
  "maxComplaintsPerVehicle": 100,
  "maxDiscoveredModelsPerFeed": 12,
  "maxEvidenceItems": 10,
  "complaintAlertThreshold": 3,
  "delivery": "dataset",
  "datasetMode": "all",
  "snapshotKey": "nhtsa-vehicle-recall-digest-state",
  "notifyOnNoNew": true,
  "requestTimeoutSeconds": 30,
  "batchDelayMs": 600,
  "dryRun": false
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Tips & Limitations

• Run daily for active watchlists; weekly for passive monitoring.
• Webhook delivery works well for compliance team Slack channels — include docket URL for 1-click access.
• Use watchKeywords generously — false positives are cheap to triage, false negatives miss filings.
• Pair with regulatory-change-monitor for cross-agency coverage.
• Archive Dataset rows weekly for long-term compliance evidence retention.

FAQ

How far back does history go?

This actor monitors forward-only — new items since first run. For historical data, use the agency's own search tool.

What timezones are used?

All timestamps are UTC. Use your downstream pipeline to convert to agency-local time if needed.

Does it translate non-English content?

No — original language is preserved. Use downstream translation services if needed.

Is the data official?

Yes — sourced directly from official government websites and feeds. Not a third-party aggregator.

Can I use this for legal research?

For alerting and monitoring, yes. For litigation research, cross-verify with primary sources (agency websites) — this actor is a monitoring tool, not a legal database.

Related Actors

Government & Regulatory cluster — explore related Apify tools:

• EPA Enforcement Digest | ECHO Compliance Risk Monitor — Monitor EPA ECHO all-media facility search, corporate compliance screener, and enforcement case feeds with one summary-first digest row per watched company, facility, or case feed.
• FDA Warning Letters Digest | Summary-First Feed — Monitor public FDA warning letters with one summary-first digest row per configured feed.
• Federal Register Digest | Agency Rule & Notice Monitor — Monitor Federal Register documents — rules, proposed rules, and notices — per configured agency feed.
• Government Contract Award Monitor | Award & Competitor Watch — Monitor public-sector contract award notices for new wins, notable awardees, incumbent recompetes, and competitor signals — one digest row per configured feed without brittle broad crawling.
• Grants.gov Funding Digest | Opportunity Watch & Signal Digest — Monitor Grants.
• Product Safety Recall Digest | CPSC + openFDA Alerts — Monitor CPSC saferproducts.
• Regulatory Change Monitor API — Monitor official regulator update feeds, government bulletin pages, and public compliance notices with one action-oriented digest row per monitored source.
• OFAC Sanctions Change Digest | SDN List Monitor — Monitor the OFAC SDN (Specially Designated Nationals) sanctions list for additions and removals.
• Tariff Trade Change Digest | Federal Register + HTS Monitor — Monitor U.
• Treasury Fiscal Data Digest | Debt, Rates & Budget Monitor — Monitor the U.
• USPTO Patent Monitor API | JSON + Webhook — Search and monitor US patent filings with multi-source fallback.
• Campaign Finance & Lobbying Digest | FEC + LDA Watch — Monitor official FEC OpenFEC committee reports and LDA.

Cost

Pay Per Event:

• actor-start: $0.01 (flat fee per run)
• dataset-item: $0.003 per output item

Example: 1,000 items = $0.01 + (1,000 × $0.003) = $3.01

No subscription required — you only pay for what you use.

⭐ Was this helpful?

If this actor saved you time, please leave a ★ rating on Apify Store. It takes 10 seconds, helps other developers discover it, and keeps updates free.

Bug report or feature request? Open an issue on the Issues tab of this actor.

Compliance Guardrails

This actor is independently operated and has no source-agency affiliation, sponsorship, or approval. It uses public data from NHTSA datasets and APIs (https://www.nhtsa.gov/nhtsa-datasets-and-apis). Results are informational only and may be delayed, incomplete, amended, withdrawn, or superseded by the source. Verify all records with the linked official source before relying on them.

• Use NHTSA public APIs/datasets only.
• Label complaint records as consumer-submitted and unverified.
• Do not state that a complaint confirms a defect or replaces official safety review.