Retrieve manufacturer technical service bulletin (TSB) and safety recall campaign data by VIN using the NHTSA API and supplementary OEM channels
domain: api.nhtsa.gov · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Query the NHTSA Recalls API with the vehicle's make, model, and year to retrieve a list of federal safety recall campaigns and their associated component categories and remedy descriptions
Use the NHTSA vPIC VIN decode API (vpic.nhtsa.dot.gov) to confirm the vehicle's exact trim and plant information, which is necessary to determine whether a specific recall applies to a VIN
Cross-reference the decoded VIN against the NHTSA recall lookup endpoint that accepts a full 17-character VIN to return only the campaigns applicable to that specific vehicle
For TSBs (which are not federal safety mandates and are not in the NHTSA recalls dataset), query a licensed TSB data provider such as ALLDATA, Mitchell1, or an equivalent commercial source, as TSBs are not available through NHTSA's public API
Display the recall status with a clear distinction between open (remedy not yet performed), closed (remedy completed), and not applicable (VIN not within the affected population), sourcing this information from the NHTSA VIN-level lookup
Implement a periodic re-check schedule (for example, weekly) since new recalls are issued continuously and a vehicle that was clear yesterday may have an open recall today
Known gotchas
NHTSA recall data covers federally mandated safety recalls only; Technical Service Bulletins are manufacturer-issued non-safety notifications and are not in any NHTSA API — licensing commercial TSB data is a separate business relationship
A recall appearing in the make/model/year lookup does not automatically mean a specific VIN is affected; always use the VIN-specific lookup endpoint to filter to affected vehicles within the production run
NHTSA public APIs have no guaranteed SLA or rate limit documentation; implement caching and graceful degradation so a NHTSA outage does not block your application's core workflows
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?