How to Scrape NHTSA Vehicle Recalls

Vehicle recall research is easy for one car and awkward for an entire fleet, catalog, or model comparison. The NHTSA Vehicle Safety Scraper converts official campaign records into consistent rows that can be searched, joined, and monitored.

Query a vehicle configuration

Provide the make, model, and model year explicitly:

{"vehicles":[{"make":"Honda","model":"Civic","modelYear":2020}],"includeRecalls":true,"includeComplaints":false,"maxResultsPerVehicle":100}

Each recall row includes the NHTSA campaign number, manufacturer, component, summary, consequence, remedy, report dates, and affected-unit count when the source provides it. The original query is retained so results remain attributable after several vehicle configurations are combined.

Use campaign number as the durable recall key. Manufacturers sometimes describe the same component differently across models, so matching on component text alone creates false merges. Preserve the source dates and collection timestamp as well. Recall information can be revised after an initial filing, and a fresh run should be able to replace an older snapshot without losing history.

For a broad catalog, split vehicles into modest batches and use a result cap that fits the expected campaign volume. An empty result means the API returned no matching campaign for that exact make, model, and year; it does not prove an individual vehicle has no unresolved service action. Model naming also matters, so normalize obvious spacing differences while retaining the submitted value for troubleshooting.

This dataset is appropriate for research, inventory screening, support workflows, and fleet prioritization. It is not a VIN-level recall lookup and should not be presented as one. For decisions about a particular vehicle, direct the owner to the official NHTSA lookup or the manufacturer and confirm the latest status before acting.