Data Sources & Methodology
Every figure on VinSpecs comes from an official U.S. government source, with the source named next to the data and a check date.
VinSpecs aggregates public U.S. government vehicle data. We pull from NHTSA vPIC (specifications), the NHTSA Recalls API (open safety campaigns), NHTSA NCAP (crash-test ratings), NHTSA complaints and investigations databases, and EPA FuelEconomy.gov (fuel economy). We ingest these sources into a local snapshot store and serve every page from it. VinSpecs is an independent service and is not affiliated with NHTSA, the EPA or any manufacturer.
How our data pipeline works
Official APIs feed an offline snapshot store (ingest runs on a schedule). Pages are rendered from that store, never from a live API call. This has three consequences for you:
- Every data block names its source, and pages show when the underlying data was last checked.
- Pages load fast and stay stable, because no figure depends on a third-party server responding at the moment you arrive.
- Data can lag by up to one refresh cycle. Recall status changes over time, so before acting on a recall, confirm by VIN with NHTSA or your dealer.
Sources we use
| NHTSA vPIC | Vehicle specifications: make, model, year, trim, engine, transmission, drivetrain, plant. Decoded per VIN via the official vPIC API (vpic.nhtsa.dot.gov/api). |
|---|---|
| NHTSA Recalls | Open safety recall campaigns by year/make/model, via the NHTSA Recalls API (nhtsa.gov/recalls). Refreshed on ingest runs; recall repairs are free at any franchised dealer for 10 years after first sale (49 U.S.C. § 30120). |
| NHTSA NCAP | Crash-test star ratings (overall, frontal, side, rollover) from the New Car Assessment Program (nhtsa.gov/ratings). |
| NHTSA Complaints | Owner-reported problems by year/make/model (nhtsa.gov/vehicle). Complaints are self-reported and are not verified by NHTSA; we show counts, the most-reported problem areas and a sample of summaries. |
| NHTSA Investigations | Defect investigations from the Office of Defects Investigation. The current NHTSA API for this data requires NHTSA-issued credentials, so it is not yet ingested; pages show nothing rather than empty guesses. Search ODI directly. |
| NHTSA Manufacturer Communications | Technical Service Bulletins (TSBs) — dealer-facing repair instructions. Same credential requirement as investigations: not yet ingested. TSBs are not recalls. |
| EPA FuelEconomy.gov | City/highway/combined MPG, fuel type and CO2 tailpipe emissions, from the official FuelEconomy.gov web service (fueleconomy.gov). |
| SAE J2012 | The OBD-II diagnostic trouble code standard behind our code lookup, consistent across all 1996-and-newer U.S. vehicles. |
Known limitations
- Recall data is snapshot-based. A campaign filed yesterday may not appear until the next ingest run. Always confirm by VIN for a vehicle you own or plan to buy.
- Not every model year has an NCAP rating. NHTSA tests a subset of vehicles each year; missing ratings are shown as missing, never guessed.
- MPG figures are EPA label values. Real-world fuel economy typically runs 10–15% below the label, depending on driving and conditions.
- Complaints are anecdotes, not verdicts. High complaint counts flag patterns worth checking; they are not proof of a defect.
- We do not have accident, title or ownership history. That data lives in paid NMVTIS-backed services. We tell you where to verify it instead of pretending to have it.
Citing VinSpecs
You are welcome to cite our pages. Cite the underlying source for the data and VinSpecs for the presentation, for example: “Source: NHTSA Recalls API, via VinSpecs.org”. Every data block on the site already names its source with a link, so citations stay traceable.
Corrections
Found a figure that contradicts the official source? Tell us with the URL and the official value. We treat a mismatch against the government API as a defect and fix it in the next ingest run.
Related: About VinSpecs · FAQ · Developer API