Use cases / Fleet managers
RecallDB for fleet managers
The problem
A fleet has dozens or hundreds of vehicles across makes and years. New recalls arrive every week, and drivers should not wait for a letter in the mail.
Decode the whole list by VIN to get the recalls filed for each make, model and year, then watch your makes and models: a webhook fires when a new NHTSA recall names one of them. Each answer links the notice and NHTSA's VIN check, where you confirm each vehicle.
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/watchlists \
-H "Authorization: Bearer $RECALLDB_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "Fleet", "makes": ["Ford", "Ram"], "models": ["Transit", "ProMaster"], "webhook_id": "wh_..."}'Free and Pro
Free (beta): 1 watchlist of up to 10 values, 1 webhook (hourly batch), 5 VINs per call. Try the free fleet check at /fleet-check (50 VINs, no signup).
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.