Use cases / Car dealers
RecallDB for car dealers
The problem
Buyers ask about recalls, and NHTSA files them by make, model and year. Looking each model up by hand is slow.
RecallDB decodes each VIN and returns the recalls filed for its make, model and year, with NHTSA's remedy text and a link to each notice, so a listing can show them. Whether a recall has been repaired on one particular car is only on NHTSA's VIN check or with a dealer, so every answer links there.
What a VIN answer covers. Recalls filed for this make, model and year. To confirm whether this vehicle's recall has been repaired, check nhtsa.gov/recalls or a dealer.
Endpoints that help
Example
curl -X POST https://recalldb.app/v1/vins/batch \
-H "Authorization: Bearer $RECALLDB_KEY" \
-H "Content-Type: application/json" \
-d '{"vins": ["1HGCM82633A004352", "2T1BURHE0JC123456"]}'Free and Pro
Free (beta): Up to 5 VINs per call and 1,000 requests a month, for evaluation.
Pro (planned): Free (beta) is for non-commercial use: build and test on it. A product or service you sell needs Pro, which is planned (commercial use, about 50,000 requests a day, instant webhooks, 100 VINs per batch call); join the waitlist and we write once when it opens.
Every answer names the agency and links its official notice. RecallDB reports what notices say; it never tells anyone that a car or product is free of recalls.