NHTSA Vehicle Safety Scraper - Recalls, Complaints & Ratings
Pricing
from $0.01 / 1,000 recall records
NHTSA Vehicle Safety Scraper - Recalls, Complaints & Ratings
Scrape NHTSA vehicle safety data by make/model/year, VIN, NHTSA id or date window: recalls with affected vehicles and PDFs, owner complaints with crash/fire/injury flags, NCAP crash-test ratings, defect investigations, service bulletins, VIN decoding. Monitor mode. No API key.
Pricing
from $0.01 / 1,000 recall records
Rating
0.0
(0)
Developer
Scrapers Delight
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
11 days ago
Last modified
Categories
Features
Share
What does NHTSA Vehicle Safety Scraper do?
NHTSA Vehicle Safety Scraper pulls US vehicle safety records from NHTSA's own public APIs: recalls, owner complaints, NCAP 5-star crash-test ratings, defect investigations, manufacturer communications (technical service bulletins), a one-row safety summary per vehicle, and VIN decoding. Look vehicles up by make, model and year, by VIN, by NHTSA id (recall campaign, complaint ODI number, investigation, bulletin), or pull everything NHTSA logged in a date window across all vehicles. Built for used-car marketplaces, dealers, insurers, fleet managers, repair shops, law firms and safety researchers.
Also known as: NHTSA recall scraper, NHTSA complaints API, vehicle recall lookup, VIN recall check, NCAP crash test ratings API.
- ๐จ Recalls with the detail other tools drop - Do Not Drive and Park Outside advisories, over-the-air fixes, units affected, every affected vehicle with production dates, and the PDF documents (Part 573 report, owner letters).
- ๐ Every owner complaint - crash, fire, injury and death flags, components, incident and filing dates, partial VIN, owner city and state, full narrative.
- โญ Crash-test ratings for every tested trim - overall, frontal, side, side pole and rollover stars, ESC / forward collision / lane departure, crash photos, videos and report PDFs.
- ๐ Investigations linked to the vehicle by NHTSA itself - Preliminary Evaluations, Engineering Analyses, Recall Queries, with documents and the recalls they led to.
- ๐ VIN in, records out - decode up to thousands of VINs (about 150 vPIC fields), then the decoded vehicle's recalls, complaints and the crash-test variant that matches the VIN.
- ๐ What's new at NHTSA - every recall, complaint and investigation logged in a date window, each completed with make, model, year and components, optionally for chosen makes only.
- ๐ Monitor mode - schedule it and get only records you have not received before.
- ๐งพ No login, no API key, no proxy needed.
What data can you get from NHTSA?
| ๐จ Recall campaign number | ๐งฉ Component path | โ Do Not Drive / Park Outside |
| ๐ Summary, consequence, remedy | ๐ข Units affected | ๐ Affected vehicles + production dates |
| ๐ Recall PDFs (Part 573, owner letters) | ๐ก Over-the-air remedy flag | ๐ Complaint ODI number + narrative |
| ๐ฅ Crash / ๐ฅ fire flags | ๐ฉน Injuries / deaths reported | ๐ Owner city + state |
| โญ Overall + frontal + side + rollover stars | ๐ฅ Crash test photos, videos, reports | ๐ก๏ธ ESC, FCW, lane departure |
| ๐ Investigation type + status | ๐๏ธ Open / close dates | ๐ง Service bulletin number + summary |
| ๐ Per-vehicle counts, top complaint components | ๐ Decoded VIN (engine, body, plant, ADAS) | ๐ฏ NCAP variant matched to the VIN |
How to scrape NHTSA with NHTSA Vehicle Safety Scraper
- Sign up for a free Apify account - the free plan includes monthly credit.
- Open NHTSA Vehicle Safety Scraper in the Apify Console.
- Pick Look up by (Vehicles, VINs, NHTSA IDs or Latest NHTSA activity) and fill the matching list, e.g.
Honda, Accord, 2020. - Choose the Record types and any filters.
- Click Start.
- Download the results as JSON, CSV, Excel or HTML, or read them through the API.
โฌ๏ธ Input
| Parameter | Type | Default | Description |
|---|---|---|---|
mode | select | vehicles | vehicles, vins, ids or recent (latest NHTSA activity). Inferred from the list you fill when an API caller leaves it out. |
vehicles | list | demo Honda, Accord, 2020 | Make, Model, Year lines. Year ranges (Ford, F-150, 2015-2018) and every model of a make (Ford, *, 2020) work. |
vins | list | - | 17-character VINs. Duplicates are removed. |
nhtsaIds | list | - | 20V771000 or 20V771 (recall), 11770490 (complaint ODI), EA24002 (investigation), MC-11037688 (bulletin). |
recordTypes | multi-select | recalls, complaints, safetyRatings, investigations | Add manufacturerCommunications (bulletins) and vehicleSummary. |
includeDetails | boolean | true | Affected vehicles + PDF documents on recall and investigation rows. |
includeVinDecode | boolean | true | VIN mode: one decoded-specification row per VIN. |
dateFrom / dateTo | string | - | YYYY-MM-DD or 30d, 12w, 6m, 1y, ytd. Latest-activity mode defaults to 7d. |
complaintSeverity | select | any | anySevere, crash, fire, crashOrFire, injury, death, injuryOrDeath. |
componentKeywords | list | - | e.g. AIR BAGS, SERVICE BRAKES, FUEL. |
keywords / excludeKeywords | list | - | Words in subject, summary, consequence or remedy. |
parkItOnly | boolean | false | Recalls with a Do Not Drive or Park Outside advisory only. |
investigationStatus | select | any | open or closed. |
minOverallRating | integer | 0 | Crash-test rows with at least this many overall stars. |
makes | list | - | Latest-activity mode: only these makes. |
monitorMode / monitorKey | boolean / string | false / - | Only records not delivered by earlier runs; a name keeps separate memories. A recall or investigation delivered without its affected vehicles and documents (includeDetails off, or the lookup failed) is delivered once more, with them, by a later run that reads them. |
maxResults | integer | 100 | Rows across all vehicles and types (shared so each vehicle gets rows). 0 = no limit. |
maxComplaintsPerVehicle | integer | 0 | Newest complaints first; 0 = all. |
includeComplaintText | boolean | true | Off = complaint rows without the narrative. |
proxyConfiguration | proxy | none | Not needed. If NHTSA ever refuses the run's IP, the run moves to Apify residential (US) within a small budget. |
API callers of other NHTSA actors can also send make / model / modelYear, vin, campaignNumbers, odiNumbers, maxItems, onlyNew and includeRecalls / includeComplaints / includeSafetyRatings / includeInvestigations.
Input JSON
{"mode": "vehicles","vehicles": ["Honda, Accord, 2020", "Ford, F-150, 2015-2016"],"recordTypes": ["recalls", "complaints", "safetyRatings", "investigations", "vehicleSummary"],"complaintSeverity": "anySevere","maxResults": 500}
Type the model the way you say it
NHTSA files some vehicles under longer names: a 2015 F-150 is filed as F-150 SUPER CREW, F-150 SUPERCAB and F-150 REGULAR CAB, and asking NHTSA for plain F-150 returns nothing. When your model name has no exact match, the actor reads every NHTSA model that starts with it and removes the duplicates (a recall shared by the three cab models is one row). The row's model shows the name NHTSA used.
VINs: what "the VIN's recalls" means
A VIN is decoded with NHTSA's vPIC decoder and the records come from the decoded make, model and year - the same as typing the vehicle. NHTSA's open APIs do not say whether a recall was already repaired on one specific VIN. For crash tests, the variant matching the VIN (drive, doors, pickup cab, side air bags) is marked matchesVin: true; when the VIN does not single one out, every tested variant is returned.
Latest NHTSA activity
mode: "recent" walks NHTSA's own lists newest first: about 250 complaints and 4 recalls are logged per day, and 4,184 investigations exist in total. Each row is completed with make, model, year and components. With makes, complaints are pre-screened by decoding their partial VIN, so only likely matches are looked up.
โฌ๏ธ Output
One row per record; recordType says which. A real recall row (Honda Accord 2020, trimmed):
{"recordType": "recall","campaignNumber": "26V332000","make": "HONDA", "model": "ACCORD", "modelYear": 2020,"subject": "Air Bags May Deploy Unintentionally During a Crash","component": "AIR BAGS:SENSOR:OCCUPANT CLASSIFICATION:FRONT PASSENGER","consequence": "Air bags that deploy unintentionally during a crash increase the risk of injury.","reportReceivedDate": "2026-05-21","potentialUnitsAffected": 98892,"parkIt": false, "parkOutside": false, "overTheAirUpdate": false,"affectedVehiclesCount": 92,"affectedVehicles": [{ "make": "ACURA", "model": "MDX", "modelYear": 2020, "productionDates": "Unknown - 12/22/2020" }],"documentsCount": 22,"documents": [{ "title": "Recall 573 Report", "url": "https://static.nhtsa.gov/odi/rcl/2026/RCLRPT-26V332-6150.pdf" }]}
A real complaint row (trimmed):
{"recordType": "complaint","odiNumber": 11770278,"make": "HONDA", "model": "ACCORD", "modelYear": 2020,"dateComplaintFiled": "2026-10-10", "dateOfIncident": "2025-09-01","crash": false, "fire": false, "numberOfInjuries": 0, "numberOfDeaths": 0,"components": "ELECTRICAL SYSTEM,AIR BAGS","vin": "1HGCV2F34LA","consumerCity": "JEFFERSON CITY", "consumerState": "TN","summary": "The Supplemental Restraint System Problem message along with the airbag light comes and goes ..."}
Fields and measured fill
Measured on the runs of 2026-10-14 (Accord 2020, F-150 2015 + Silverado 1500 2020, six VINs, a 7-day window):
| Record | Fields always filled | Partly filled (why) |
|---|---|---|
| recall | campaign, subject, component path, summary, consequence, remedy, report date, units affected, park-it / park-outside / OTA, affected vehicles, documents | mfrCampaignNumber 80% (NHTSA writes "Refer to Comments"), notes 80% |
| complaint | ODI number, filing + incident dates, crash, fire, injuries, deaths, components, narrative | partial vin 92-98%, owner city/state 69-100% (not every owner gives one) |
| safetyRating | variant, overall / frontal / side / rollover stars, ESC, FCW, LDW, report PDFs | side pole, combined ratings, videos 55-100% (not every variant had every test) |
| investigation | number, type + label, status, subject, plain-text summary, open date, components | close date (open ones have none) |
| manufacturerCommunication | bulletin number, NHTSA id, summary, date, components | PDF documents only on id lookups |
| vehicleSummary | every count, top 5 complaint components, NCAP best/worst | - |
| vinDecode | VIN, decoded, error code/text, make, model, year | ~40-75 of ~150 vPIC fields per VIN (vPIC leaves the rest blank) |
Not shipped: rolloverPossibility2 (NHTSA returns 0.0 on every record we sampled - a placeholder, not a probability); a bulletin's manufacturer component system and communication type (only in a separate NHTSA flat file, not the API).
Use cases
- ๐ Used-car marketplaces and dealers - show open recalls and crash ratings on every listing; flag Do Not Drive recalls.
- ๐ก๏ธ Insurers and fleet managers - screen VIN lists for recalls, investigations and complaint trends.
- ๐ง Repair shops - pull service bulletins and complaint patterns before diagnosing a car.
- โ๏ธ Law firms and researchers - every complaint with crash, fire, injury and death flags, plus investigation documents.
- ๐ Manufacturers and suppliers - monitor new complaints and investigations for your makes every day.
- ๐ฐ Journalists - what NHTSA logged this week, across every vehicle.
How much does it cost to scrape NHTSA?
Pay per record delivered, no start fee:
| Record | Price |
|---|---|
| Recall | $0.00001 |
| Complaint | $0.00045 |
| Crash-test rating | $0.00045 |
| Investigation | $0.009 |
| Service bulletin | $0.0018 |
| Vehicle summary | $0.0018 |
| VIN decoded | $0.000045 (VINs that do not decode are free) |
| Run | Rows | Price |
|---|---|---|
| Prefilled demo (Accord 2020, 20 rows) | 5 recalls, 13 complaints, 1 rating, 1 investigation | ~$0.015 |
| One vehicle, default record types (Accord 2020) | 5 recalls, 364 complaints, 1 rating, 1 investigation | ~$0.17 |
| Two pickups, every record type (F-150 2015 + Silverado 1500 2020) | 4,004 rows incl. 1,793 bulletins | ~$4.28 |
| A week of new complaints, all makes (NHTSA logs ~250 a day) | ~1,750 | ~$0.79 |
Rows removed by your filters, duplicates and rows a monitor already delivered are never delivered or charged. Set maxResults or a maximum charge per run to cap spending.
Integrations, API, scheduling & MCP
Schedule a daily run with monitorMode on to receive only new recalls and complaints, and send them to Google Sheets, Slack, Make, Zapier or n8n through Apify integrations or webhooks. Call it from code with the Python or JavaScript client, or the actor's API tab. AI agents can use it through the Apify MCP server (https://mcp.apify.com).
More vehicle and registry scrapers
- JDM VIN Decoder - Japanese chassis numbers to production date and options.
- Bring a Trailer Scraper - sold prices and VINs from BaT auctions.
- Cars.com Dealer Scraper - US car dealer leads.
- FMCSA Carrier Scraper - USDOT / MC carriers with contacts.
- FAA Aircraft Registry Scraper - registered aircraft and owners.
- All ScrapersDelight actors
Limits & empty runs
- Speed (2026-10-14): the 20-row demo in 3-10 s; 100 rows in ~3 s once NHTSA's cache is warm; 4,004 rows (two pickups, every record type) in 45 s.
- NHTSA's API refuses an IP that sends bursts (about 100 requests in a second). The actor paces itself at 6 requests per second and pauses on a refusal.
- A vehicle NHTSA does not list is reported as not found in
RUN_SUMMARY; a vehicle with no records returns no rows. Neither is charged. - If NHTSA cannot be reached at all, the run fails instead of returning "no records".
โ FAQ
How much does NHTSA Vehicle Safety Scraper cost?
You pay per record delivered (table above), with no start fee. The 20-row demo costs about $0.015; a whole vehicle with all 364 complaints about $0.17.
Can NHTSA Vehicle Safety Scraper check recalls by VIN?
Yes. Put VINs in vins: each is decoded and the decoded vehicle's recalls, complaints and crash tests are returned, with the matching crash-test variant marked. NHTSA's open APIs do not say whether a specific VIN's recall was already repaired.
Does NHTSA Vehicle Safety Scraper return complaints with crash and injury data?
Yes. Every complaint has crash, fire, numberOfInjuries and numberOfDeaths as the owner reported them, and complaintSeverity keeps only the serious ones.
Can I look up a recall campaign or complaint number with NHTSA Vehicle Safety Scraper?
Yes. nhtsaIds takes recall campaigns (20V771 or 20V771000), complaint ODI numbers, investigation numbers (EA24002) and bulletins (MC-11037688).
Can NHTSA Vehicle Safety Scraper give me only new recalls each day?
Yes. Turn on monitorMode and schedule the run; records an earlier run delivered are skipped and not charged. For the whole database, use Latest NHTSA activity with dateFrom: "1d".
Why did NHTSA Vehicle Safety Scraper return no results for my model?
Check the year and make; the actor already tries NHTSA's longer model names (F-150 -> F-150 SUPER CREW). RUN_SUMMARY lists each vehicle as found, not found or unreachable, and filters that removed rows.
Does NHTSA Vehicle Safety Scraper need an NHTSA API key or login?
No. It reads NHTSA's public APIs (api.nhtsa.gov and vpic.nhtsa.dot.gov). No key, login or proxy.
Can I use NHTSA Vehicle Safety Scraper through the Apify API or an MCP server?
Yes - the API tab shows ready-made calls, and the Apify MCP server exposes it to AI agents.
Are the injury and death counts verified?
No. They are what the owner reported to NHTSA, unverified.
Is it legal to scrape NHTSA data?
NHTSA publishes these records through its own public APIs with no login. This is an independent tool, not affiliated with NHTSA.
Your feedback
Missing a field or a record type? Open an issue on the actor's Issues tab and we will look at it.