Skip to main content

NHTSA Datasets and APIs

In Support of Open Government Directive

Complaints

Complaint information entered into NHTSA’s Office of Defects Investigation vehicle owner's complaint database is used with other data sources to identify safety issues that warrant investigation and to determine if a safety-related defect trend exists. Complaint information is also analyzed to monitor existing recalls for proper scope and adequacy.

Dataset Summary

Agency: Department of Transportation
Sub-Agency/Organization: National Highway Traffic Safety Administration
Category: 23, Transportation
Date Released: December 16, 2002
Time Period: 1949 to present
Frequency: Daily

Dataset Information

Data.gov Data Category Type: Raw data
Specialized Data Category Designation: Enforcement
Keywords: Phone, Paper, Email
Unique ID: 81

Contributing Agency Information

Citation: N/A
Agency Program Page: http://www-odi.nhtsa.dot.gov/downloads/index.cfm
Agency Data Series Page http://www-odi.nhtsa.dot.gov/downloads/folders/Complaints/FLAT_CMPL.zip

Dataset Coverage

Unit of Analysis: Vehicles, Tires, Child Safety Seats, Equipment
Granularity: United States
Geographic Coverage: N/A

Data Description

Collection Mode: Web, Phone
Data Collection Instrument: N/A
Data Dictionary/Variable List: http://www-odi.nhtsa.dot.gov/downloads/folders/Complaints/CMPL.txt

Dataset Quality

Data Quality Certification: Yes
Privacy and Confidentiality: Yes
Applicable Information Quality Guideline Designation: National Highway Traffic Safety Administration

Additional Dataset Documentation

Technical Documentation: http://www-odi.nhtsa.dot.gov/downloads/folders/Complaints/Import_Instructions.pdf

Additional Metadata: N/A

Approach A: Get by Model Year, Make, Model

Make the request to get the complaints for the required combination of Model Year, Make and Model.

  • Syntax: api.nhtsa.gov/complaints/complaintsByVehicle?make={MAKE}&model={MODEL}&modelYear={MODEL_YR}
  • Example: https://api.nhtsa.gov/complaints/complaintsByVehicle?make=acura&model=rdx&modelYear=2012

Response Fields: Response is a list of complaints for the given Model Year, Make and Model

Working Sample: JSON

 


 

Approach B: Get by Model Year, Make, Model

Step 1: Get all Model Years    

Request a list of available Model Years for a given product type (Vehicle).

  • Syntax: api.nhtsa.gov/products/vehicle/modelYears?issueType=c
  • Example: https://api.nhtsa.gov/products/vehicle/modelYears?issueType=c

Response Fields: Response is a list of available Model Years in the repository. Use a Model Year from this list to use in the next step. 

Working Sample: JSON

 

Step 2: Get all Makes for the Model Year

Request a list of vehicle Makes by providing a specific vehicle Model Year.

  • Syntax: api.nhtsa.gov/products/vehicle/makes?modelYear={year}&issueType=c
  • Example: https://api.nhtsa.gov/products/vehicle/makes?modelYear=2021&issueType=c

Response Fields: Response is a list of vehicle Makes for that Model Year. Use the Model Year and a Make from this list to use in the next step.

Working Sample: JSON

 

Step 3: Get all Models for the Make and Model Year

Request a list of vehicle Models by providing the vehicle Model Year and Make.

  • Syntax: api.nhtsa.gov/products/vehicle/models?modelYear={year}&make={make}&issueType=c
  • Example: https://api.nhtsa.gov/products/vehicle/models?modelYear=2010&make=acura&issueType=c

Working Sample: JSON

 

Step 4: Get all complaints for the selected Model Year, Make, Model    

Now that you have all three key pieces of information (Model Year, Make, Model), make the request to get the complaints for the required combination.

  • Syntax: api.nhtsa.gov/complaints/complaintsByVehicle?make={MAKE}&model={MODEL}&modelYear={MODEL_YR}
  • Example: https://api.nhtsa.gov/complaints/complaintsByVehicle?make=acura&model=rdx&modelYear=2012

Response Fields: Response is a list of complaints for the given Model Year, Make and Model 

Working Sample: JSON

 


 

Approach C: Get by ODI Number

Request a list of complaints by providing ODI number.

  • Syntax: api.nhtsa.gov/complaints/odinumber?odinumber={odinumber}
  • Example: https://api.nhtsa.gov/complaints/odinumber?odinumber=11184030

Response Fields: Response is a list of complaints for the specified ODI number.

Working Sample: JSON


Notes

Color codes to understand each part of the request URL:

  • Red: Method Name
  • Green: Applicable parameters

Request parameters and method names are case sensitive

Recalls

Manufacturers who determine that a product or piece of original equipment either has a safety defect, or is not in compliance with federal safety standards, are required to notify NHTSA within five business days. NHTSA requires that manufacturers file a defect and noncompliance report as well as quarterly recall status reports, in compliance with Federal Regulation 49 (the National Traffic and Motor Safety Act) Part 573, which identifies the requirements for safety recalls. NHTSA stores this information and the data can be used to search for recall information related to specific NHTSA campaigns and product types.

Dataset Summary

Agency: Department of Transportation
Sub-Agency/Organization: National Highway Traffic Safety Administration
Category: 23, Transportation
Date Released: December 16, 2002
Time Period: 1949 to present
Frequency: Daily

Dataset Information

Data.gov Data Category Type: Raw data
Specialized Data Category Designation: Research
Keywords: Phone, Paper, Email
Unique ID: 83

Contributing Agency Information

Citation: N/A
Agency Program Page: http://www-odi.nhtsa.dot.gov/downloads/index.cfm
Agency Data Series Page: http://www-odi.nhtsa.dot.gov/downloads/folders/Recalls/FLAT_RCL.zip

Dataset Coverage

Unit of Analysis: Vehicles, Tires, Child Safety Seats, Equipment
Granularity: United States
Geographic Coverage: N/A

Data Description

Collection Mode: N/A
Data Collection Instrument: N/A
Data Dictionary/Variable List: http://www-odi.nhtsa.dot.gov/downloads/folders/Recalls/RCL.txt

Dataset Quality

Data Quality Certification: Yes
Privacy and Confidentiality: Yes
Applicable Information Quality Guideline Designation: National Highway Traffic Safety Administration

Additional Dataset Documentation

Technical Documentation: http://www-odi.nhtsa.dot.gov/downloads/folders/Recalls/RCL.txt
Additional Metadata: N/A

Approach A: Get by Model Year, Make, Model

Make the request to get the recalls for the required combination of Model Year, Make and Model.

  • Syntax: api.nhtsa.gov/recalls/recallsByVehicle?make={MAKE}&model={MODEL}&modelYear={MODEL_YR}
  • Example:https://api.nhtsa.gov/recalls/recallsByVehicle?make=acura&model=rdx&modelYear=2012

Response Fields: Response is a list of recalls for the given Model Year, Make and Model.

Working Sample: JSON

 


 

Approach B: Get by Model Year, Make, Model

Step 1: Get all Model Years

Request a list of available Model Years for a given product type (Vehicle).

  • Syntax: api.nhtsa.gov/products/vehicle/modelYears?issueType=r
  • Example: https://api.nhtsa.gov/products/vehicle/modelYears?issueType=r 

Working Sample: JSON

 

Step 2: Get all Makes for the Model Year

Request a list of vehicle Makes by providing a specific vehicle Model Year.

  • Syntax: api.nhtsa.gov/products/vehicles/makes?modelYear={year}&issueType=r
  • Example: https://api.nhtsa.gov/products/vehicle/makes?modelYear=2021&issueType=r

Response Fields: Response is a list of vehicle Makes for that Model Year. Use the Model Year and a Make from this list to use in the next step.

Working Sample: JSON

 

Step 3: Get all Model for the Make and Model Year

Request a list of vehicle Models by providing the vehicle Model Year and Make.

  • Syntax: api.nhtsa.gov/products/vehicle/models?modelYear={year}&make={make}&issueType=r
  • Example: https://api.nhtsa.gov/products/vehicle/models?modelYear=2010&make=acura&issueType=r

Working Sample: JSON

 

Step 4 : Get all Recalls for the selected Model Year, Make, Model

Now that you have all three key pieces of information (Model Year, Make, Model), go ahead and make the request to get the recalls for the required combination.

  • Syntax: api.nhtsa.gov/recalls/recallsByVehicle?make={MAKE}&model={MODEL}&modelYear={MODEL_YR}
  • Example: https://api.nhtsa.gov/recalls/recallsByVehicle?make=acura&model=rdx&modelYear=2012

Response Fields: Response is a list of recalls for the given Model Year, Make and Model.

Working Sample: JSON

 


 

Approach C. Get by NHTSA Campaign Number

Get all recalls as part of a NHTSA recall campaign number

Request a list of recalls by providing the NHTSA recall campaign number

  • Syntax: api.nhtsa.gov/recalls/campaignNumber?campaignNumber ={campaignNumber}
  • Example: https://api.nhtsa.gov/recalls/campaignNumber?campaignNumber=12V176000

Response Fields: Response is a list of recalls for the specified NHTSA recall campaign number.

Working Sample: JSON


Notes

Color codes to understand each part of the request URL:

  • Red: Method Name
  • Green: Applicable parameters

Request parameters and method names are case sensitive

View recalls by manufacturer interactive dashboard.

Ratings

NHTSA's New Car Assessment Program rates vehicles to determine crashworthiness and rollover safety. The safety ratings are gathered during controlled crash and rollover tests conducted at NHTSA research facilities. Vehicles with a rating of five stars indicate the highest safety rating, whereas a one star indicates the lowest rating. NCAP provides consumers with important information in making a new car purchase, and for comparable vehicle models, it provides a direct comparison of the crashworthiness of vehicles. Information from this program also exists on the required labels on each new vehicle for sale.

Dataset Summary

Agency: Department of Transportation
Sub-Agency/Organization: National Highway Traffic Safety Administration
Category: 23, Transportation
Date Released: January 5, 2010
Time Period: 1990 to present
Frequency: Annual

Dataset Information

Data.gov Data Category Type: Raw data
Specialized Data Category Designation: Research
Keywords: New, Car, Assessment, Program, NCAP, Five, 5, Star, Safety, Rating, Ratings
Unique ID: 5

Dataset Coverage

Unit of Analysis: Vehicles
Granularity: N/A
Geographic Coverage: N/A

Dataset Quality

Data Quality Certification: No
Privacy and Confidentiality: No
Applicable Information Quality Guideline Designation: National Highway Traffic Safety Administration

Approach A. Get by Model Year, Make, Model

Step 1: Get available vehicle variants for a selected Model Year, Make and Model

Make the request to get the crash tested vehicle variants for the Model Year, Make and Model combination.

  • /SafetyRatings/modelyear/2013/make/Acura/model/rdx

Response Fields: Response is a list of vehicle variants for Model Year, Make and Model with their VehicleId and description of the variant.

Working Sample: JSON

Step 2: Get the Safety Ratings for the selected variant    

Now that you have the VehicleId of the precise model that you to look up, go ahead and make the request to get the Safety Ratings for the required vehicle variant by passing in the VehicleId.

  • /SafetyRatings/VehicleId/7520

Response Fields: Response is a list of Safety Ratings for the given vehicle variant.

Working Sample: JSON


Approach B. Get by Model Year, Make, Model

Step 1: Get all Model Years

Request a list of available Model Years for a given product type (Vehicle).

  • /SafetyRatings

Response Fields: Response is a list of available Model Years in the repository. Use a Model Year from this list to use in the next step.

Working Sample: JSON

Step 2: Get all Makes for the Model Year

Request a list of vehicle Makers by providing a specific vehicle ModelYear.

  • /SafetyRatings/modelyear/2013

Response Fields: Response is a list of vehicle Makers for that Model Year. Use the Model Year and a Maker from this list to use in the next step.

Working Sample: JSON

Step 3: Get all Model for the Make and Model Year

Request a list of vehicle Models by providing the vehicle Model Year and Maker.

  • /SafetyRatings/modelyear/2013/make/Acura

Response Fields:  Response is a list of Safety Ratings for the given Model Year, Maker and Model

Working Sample: JSON

Step 4: Get available vehicle variants for a selected Model Year, Make and Model

Make the request to get the crash tested vehicle variants for the Model Year, Maker and Model combination.

  • /SafetyRatings/modelyear/2013/make/Acura/model/rdx

Response Fields: Response is a list of vehicle variants for Model Year, Maker and Model with their VehicleId and description of the variant.

Working Sample: JSON

Step 5: Get the Safety Ratings for the selected variant

Now that you have the VehicleId of the precise model that you to look up, go ahead and make the request to get the Safety Ratings for the required vehicle variant by passing in the VehicleId.

  • /SafetyRatings/VehicleId/7520

Response Fields: Response is a list of Safety Ratings for the given vehicle variant.

Working Sample: JSON


Notes

Color codes to understand each part of the request URL:

  • Red: Method Name
  • Green: Applicable parameters

Request parameters and method names are case sensitive

Car Seat Inspection Locator

Car crashes are a leading cause of death and injuries for children. Data show a high number of child car seats are not installed properly. Car seat inspection stations make it easier for parents and caregivers to check to see if their car seat is installed correctly. NHTSA provides information to help people locate a car seat inspection station. Information for each station is reported to NHTSA and we attempt to validate the station locations using a commercial geographic database so this data will, in most cases, be able to be used for driving directions.

Dataset Summary

Agency: Department of Transportation
Sub-Agency/Organization: National Highway Traffic Safety Administration
Category: 23, Transportation
Date Released: November 5, 2021
Time Period: Current
Frequency: Annual

Dataset Information

Data.gov Data Category Type: Raw data
Specialized Data Category Designation: Research
Keywords: Child Seat, Safety, Inspection, Stations, Station
Unique ID: 80

Contributing Agency Information 

Agency program page: www.nhtsa.gov/equipment/car-seats-and-booster-seats#installation-help-inspection

Dataset Coverage

Unit of Analysis: N/A
Granularity: Nationwide, including Territories
Geographic Coverage: Zip, State, Geo Coordinates

Dataset Quality

Data Quality Certification: No
Privacy and Confidentiality: No
Applicable Information Quality Guideline Designation: National Highway Traffic Safety Administration

Approach A. Get by Zip Code

Make the request with a zip code to get the list of CSSIStations at the specific zip code only (nearby zip codes are not included).

  • /CSSIStation/zip/63640

Response Fields: Response is a list of CSSIStations for a given zip code.

Working Sample: JSON


Approach B. Get by State

Make the request with the state abbreviation to get the list of CSSIStations in that state only.

  • /api/CSSIStation/state/NV

Response Fields: Response is a list of CSSIStations in a given state.

Working Sample: JSON


Approach C. Get by Geo location

Make the request with an interested latitude and longitude location along with the miles nearby to look out for CSSIStations.

  • /CSSIStation?lat=30.1783&long=-96.3911&miles=50

Response Fields: Response is a list of CSSIStations nearby the interested geographical location spotted by its latitude and longitude.

Working Sample: JSON


Filters. Optional Filters

Filter 1: Filter by Spanish speaking Stations

Make the request with a zip code/state/geographical location to get the list of CSSIStations filtered by spanish speaking (attach string - /lang/spanish) and stations participating in CPSWeek event (attach string - /cpsweek). Below filters in the request string are optional, either one/none OR both can be sent in.

  • /CSSIStation/zip/67951/lang/spanish

Response Fields: Response is a list of CSSIStations for a given zip code applying the respective filter.

Working Sample: JSON

Filter 2: Filter by Stations participating in CPSWeek

Make the request with a zip code/state/geographical location to get the list of CSSIStations filtered by stations participating in CPSWeek event (attach string - /cpsweek). Below filters in the request string are optional, either one/none OR both can be sent in.

  • /CSSIStation/zip/37066/cpsweek

Response Fields: Response is a list of CSSIStations for a given zip code applying the respective filter.

Working Sample: JSON


Notes

Color codes to understand each part of the request URL:

  • Red: Method Name
  • Green: Applicable parameters
  • Orange: Extended parameters 

Request parameters and method names are case sensitive