Vehicle Safety Report — NHTSA Recalls + Complaints

A used-car buyer, dealer, or fleet manager currently checks recalls and complaints separately — NHTSA's own site requires two different lookups and returns raw lists with no combined verdict. Both are free, public, keyless. This combines them into one report per make/model/year: recall severity (NHTSA's own "do not drive" flag) and complaint patterns (crash/fire/injury/death counts, not a raw list to read one by one).

Input

{ "vehicles": [{ "make": "Honda", "model": "Accord", "modelYear": "2023" }] }

All three fields are required — NHTSA's API needs make, model, and year together to return results.

Sample output

{
  "make": "Honda",
  "model": "Accord",
  "modelYear": "2018",
  "recallCount": 6,
  "recallSeverity": "standard",
  "recallSeverityNote": "Recalls exist but none carry NHTSA's do-not-drive or park-outside flags.",
  "totalComplaints": 1863,
  "complaintsInvolvingCrash": 35,
  "complaintsInvolvingFire": 4,
  "totalDeathsReported": 0,
  "topComplaintComponents": "ENGINE (245); FORWARD COLLISION AVOIDANCE (149); FUEL SYSTEM, GASOLINE (132)"
}

The three recall severity levels

Severity	Meaning
do_not_drive	NHTSA's own flag — at least one recall says stop driving until repaired
park_outside_only	NHTSA's own fire-risk flag — park away from structures
standard	Recalls exist, no elevated NHTSA flag
none	No open recalls on file

Typical uses

• Used-car buying research — check a specific make/model/year before purchase, beyond just "how many recalls."
• Dealer inventory screening — flag inventory with do_not_drive or park_outside_only recalls before it's sold.
• Fleet management — audit a fleet's makes/models/years for open safety issues in bulk.
• Insurance/claims research — complaint patterns (crash/fire rates) are a real risk signal.

Pricing

$0.003 per vehicle report.

⚠️ Read before you act

• Complaint counts are model-year-wide, not VIN-specific. NHTSA doesn't offer VIN-level complaint lookup — this reflects the pattern across every 2018 Honda Accord filed with NHTSA, not confirmation any specific car has the issue. It's a real signal about that model-year, not a single-vehicle history report.
• Recall severity flags are NHTSA's own classification, passed through directly — never re-derived or guessed.
• This does not check open recalls for a specific VIN (NHTSA has a separate VIN-lookup endpoint not covered here) — it's a model-year-wide report.

FAQ

• Do I need an API key? No — NHTSA's API is free and keyless.
• Why do complaint numbers look high? NHTSA logs every consumer complaint nationwide for that model-year — even a well-regarded model can show hundreds or thousands over its production life. Compare crash/fire counts and top components, not the raw total, for a real risk read.
• What if my make/model/year has zero data? That's a real, valid answer — not every vehicle has recalls or logged complaints.

Related actors

• Recall Exposure Monitor — the same combined-official-feed pattern, for CPSC consumer product recalls instead of vehicles.
• Financial Complaint Monitor — the same crash/fire-style pattern aggregation, for CFPB financial complaints.

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• Vehicle Safety Report — NHTSA Recalls + Complaints declares all 15 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of Vehicle Safety Report include make, model, modelYear, recallCount, recallSeverity and recallSeverityNote.
• Vehicle Safety Report needs no API key, login or account of any kind before its first run.
• Every one of Vehicle Safety Report's 1 inputs is optional, so it runs with no configuration at all.
• Vehicle Safety Report documents totalInjuriesReported as: Injuries reported in connection with this item.
• Every number published about Vehicle Safety Report is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• Vehicle Safety Report is filed under developer tools and business so that it is found by the people looking for that job, not by its internal name.

Limitations

• Vehicle Safety Report reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.