Look up recall details and affected components for a known NHTSA recall campaign number using the Recalls API

domain: api.nhtsa.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Obtain the 9-character NHTSA recall campaign number (e.g., from a prior recallsByVehicle lookup or a manufacturer notice)
  2. Call the recalls endpoint's campaign-number query with that ID to retrieve the full recall record
  3. Parse the response for the affected component, defect summary, consequence, remedy description, and manufacturer notification dates
  4. Cross-reference the campaign number against a specific VIN's recall list (recallsByVehicle) if you need to confirm a given vehicle is actually in scope, since campaign lookups return all vehicles the campaign covers, not a single VIN's status
  5. Cache campaign-level data (component/remedy text rarely changes) separately from per-VIN open/closed status, which can change as remedies are completed

Known gotchas

Related routes

Look up vehicle recalls via the NHTSA API
api.nhtsa.gov · 6 steps · unrated
Retrieve full detail for a specific NHTSA recall campaign number tied to a windshield/camera/glazing defect, once the campaign ID is already known.
api.nhtsa.gov · 4 steps · unrated
Check open safety recalls for a vehicle using the NHTSA Recalls API
api.nhtsa.gov · 5 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans