NHTSA safety recalls for a vehicle model, by VIN or by make, model and model year: campaign number, component, summary, consequence, remedy and park-it advisories, newest first.
curl -X POST "https://api.primaryapi.com/v1/run/vin.recalls" \
-H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"make":"honda","model":"accord","modelYear":2003}'{
"output": {
"found": true,
"data": {
"count": 24,
"nextCursor": null,
"vehicle": {
"vin": null,
"make": "HONDA",
"model": "ACCORD",
"modelYear": 2003
},
"recalls": [
{
"title": "VEHICLE SPEED CONTROL:ACCELERATOR P…",
"agency": "nhtsa",
"date": "2019-10-10",
"category": "vehicle", …
}
]
}
},
"credits": 1
}Input and output
4 fields
honda.accord.2003.4 fields
Good to know
Recalls are listed per vehicle model. Year (NHTSA does not publish per-VIN repair status in this API).
A VIN costs the same as make/model/year.
One that cannot be decoded to a make, model and year is a free miss. A miss is an answer, not an error, and it costs nothing.
Rows use the same item shape as recalls.search (agency "nhtsa") plus NHTSA fields.
Newest report first, ties by campaign number.
A new campaign for the model changes the output. So a monitor on a VIN reports it.
The same key and credits work for every API.