NHTSA Vehicle Complaints Scraper
Pricing
from $19.00 / 1,000 results
NHTSA Vehicle Complaints Scraper
Scrapes NHTSA vehicle safety complaints for a given make, model, and model year. Returns each complaint as a flat row with failure date, odometer, VIN, component, narrative, and severity flags.
Pricing
from $19.00 / 1,000 results
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
9 days ago
Last modified
Categories
Share
NHTSA Vehicle Complaints Scraper
Scrape NHTSA vehicle safety complaints by make, model, and year, up to a million per run. Each complaint includes the failure date, odometer reading, VIN, incident description, and injury indicators. No API key or registration. Export to CSV, JSON, Excel, or XML.
The NHTSA public complaints database holds millions of owner-reported safety defects, but the official web interface forces you to search one query at a time and offers no bulk export. This Actor reads the complaint listings directly for any make, model, and model year you specify, returning every matching record in a consistent flat schema so you can spot defect patterns across entire vehicle lines.
| Who uses it | What they scrape NHTSA for |
|---|---|
| Automotive quality engineers | Monitor emerging defect patterns for a specific vehicle platform before a recall is issued. |
| Lemon law attorneys | Gather evidence of known defects for a particular make, model, and year to support client cases. |
| Used car dealers and inspectors | Check the complaint history of a vehicle model before purchasing inventory. |
| Safety researchers | Analyze complaint volumes and failure types across model years for trend reports. |
What it does
This Actor collects NHTSA vehicle safety complaints for a given make, model, and model year and returns each complaint as a flat row with failure details, dates, and severity flags.
- 🔍 Targeted search: Pick one make, one model, and one model year per run. Run multiple configurations in parallel for broader coverage.
- 📋 Structured output: Every complaint row includes the failure date, odometer reading, VIN (when available), component, and a full incident narrative.
- ⚠️ Severity flags: The dataset captures fire, crash, and injury indicators so you can filter for the most serious incidents immediately.
- 📊 Bulk extraction: Paid users can pull up to a million complaints per run, enough to cover decades of data for a high-volume model.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with NHTSA data
📈 Detect pre-recall defect patterns.
A quality engineer runs the Actor weekly for a 2023 SUV model, plots complaint counts by component, and flags a steering issue to the investigations team before the NHTSA opens an official inquiry.
⚖️ Build evidence for a lemon law case.
An attorney scrapes all complaints for a 2021 sedan, filters for transmission failures with injury flags, and attaches the dataset as an exhibit showing the manufacturer knew about the defect.
🚗 Vet a used car model before buying inventory.
A dealership buyer runs the Actor for three model years of a popular pickup, reviews the top failure categories, and decides to avoid the 2019 model year due to repeated engine complaints.
📝 Feed a vehicle reliability dashboard.
A data analyst schedules monthly scrapes for the top 20 selling models, pipes the CSV into a BI tool, and publishes a public-facing reliability index updated with fresh NHTSA data.
Why choose this scraper
| What you get | |
|---|---|
| No API key needed | Reads the public NHTSA complaint pages directly with no registration, OAuth, or rate-limit headaches. |
| Fixed flat schema | Every complaint lands in your dataset with the same columns, whether it has a VIN or not, so your analysis never breaks. |
| Runs on Apify infrastructure | Schedule recurring runs, get failure alerts, and store results in Apify's cloud without managing servers. |
How it compares
Three other Apify actors also access NHTSA data, each with a different scope. This Actor focuses exclusively on bulk complaint extraction by make, model, and year.
| Feature | ParseForge | NHTSA Vehicle Complaints Scraper | NHTSA Vehicle Intelligence | Product Safety Consumer Risk MCP Server |
|---|---|---|---|---|
| Bulk complaint extraction by make, model, year | Yes | Yes | Not listed | Not listed |
| VIN decoding | Not listed | Not listed | Yes | Not listed |
| Safety recall lookups | Not listed | Not listed | Yes | Not listed |
| NCAP crash test ratings | Not listed | Not listed | Yes | Not listed |
| Multi-agency safety data (CPSC, FDA, CFPB) | Not listed | Not listed | Not listed | Yes |
| Fire, crash, and injury severity flags | Yes | Not listed | Not listed | Not listed |
Configure the run
Drive the Actor with a make, model, and model year. Each run targets one vehicle configuration, so run multiple instances side by side to cover an entire brand lineup. The Input tab lists every parameter.
A first run with the defaults:
A larger pull:
Pricing
Pay-per-result: $0.021 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $2.10 |
| 1,000 results | $21.00 |
| 10,000 results | $210.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the NHTSA Vehicle Complaints Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to NHTSA through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Check that the make, model, and model year combination is valid and matches the NHTSA database exactly. Try a broader search first (e.g., a different model year) to confirm the Actor is working, then narrow down. Some low-volume models genuinely have zero complaints.
The Actor returns fewer complaints than I expected.
The NHTSA site only shows complaints filed by vehicle owners. A model with a known recall may still have few complaints if owners did not report them. Also confirm you are using a paid plan if you need more than the 10-complaint preview.
Some fields like VIN are empty in my results.
The VIN and some other fields are optional in the NHTSA database. They appear only when the owner included them in the original complaint. This is expected behavior, not a scraping error.
The run fails with a timeout.
High-volume models can have tens of thousands of complaints. Increase the run timeout in your Apify actor settings, or reduce the maxItems to a smaller number and paginate across multiple runs.
I need complaints for a vehicle not sold in the US.
The NHTSA database covers vehicles sold or registered in the United States. Vehicles manufactured for other markets may not appear. Check the NHTSA website directly to confirm coverage before running the Actor.
FAQ
| Question | Answer |
|---|---|
| What data does each complaint row contain? | Each row includes the complaint ID, failure date, odometer reading, VIN (when the owner provided it), vehicle component, a full narrative description of the incident, and boolean flags for fire, crash, injuries, and fatalities. |
| Can I scrape multiple makes or models in one run? | Each run targets one make, one model, and one model year. To cover multiple vehicles, run the Actor in parallel with different input configurations or loop over a list using Apify's task scheduling. |
| Is there a limit on how many complaints I can scrape? | Free accounts are limited to a 10-complaint preview. Paid Apify plans can pull up to one million complaints per run, which covers the full complaint history for most vehicle configurations. |
| Does this Actor require an NHTSA API key? | No. It reads the public NHTSA complaint search pages directly, so there is no API key, no registration, and no rate-limit negotiation. |
| What is the earliest model year I can search? | The input accepts model years from 1949 onward, which covers the earliest records in the NHTSA database. |
| Does the Actor return the VIN for every complaint? | The VIN field is included in the output schema, but it is only populated when the vehicle owner provided it in their complaint. Many complaints omit the VIN. |
| Can I filter complaints by component or severity inside the Actor? | The Actor returns all complaints for the selected make, model, and year. Filter by component, fire, crash, or injury flags after the run using your dataset tool or spreadsheet. |
| How do I scrape complaints for an entire brand? | Run the Actor once per model and model year combination. You can automate this by creating multiple tasks or using an Apify workflow that iterates over a list of inputs. |
| What export formats are supported? | You can export the results to CSV, JSON, Excel, XML, or push them directly to a webhook or cloud storage integration. |
| Is this Actor suitable for production monitoring? | Yes. Schedule it to run daily or weekly on Apify, and new complaints will accumulate in your dataset. You can set up alerts if a run fails or if the complaint count spikes. |
Related actors
Browse the full ParseForge collection for more scrapers.
🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by National Highway Traffic Safety Administration. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
