VIN Decoder & Recalls API - NHTSA Vehicle Lookup
Paste VINs into your AI chat and get the vehicles and their recalls back.
Paste in VINs, up to 1,000 a run, and get one row per vehicle: what the federal record says it is, where it was built, and the US safety recalls filed against its make, model and year. The details come from NHTSA's public decoder, which is built from what manufacturers file for the vehicles they sell in the US. So a car built for another market decodes partly, or not at all.
Who decodes VINs in bulk
- Wholesale buyers with an auction run list. Three hundred VINs arrive the night before a sale. Decoded, they give year, trim, engine and drive in columns you can sort, and
recallCountshows which models have campaigns worth asking the seller about. - Claims and underwriting desks. The form says a 2019 SUV and the VIN says a 2016 pickup. Make, model, year and body class straight from the VIN give you something to check the paperwork against, without retyping anything.
- Fleets checked on a schedule. Run the same list every month and compare campaign numbers with last month's. A number you haven't seen before is a new recall for that model.
A worked example
On 4 November a two-VIN run took about three seconds. The first VIN in it, 1HGCM82633A004352, is the first one the input form opens with.
It came back as a 2003 Honda Accord EX-V6 coupe, gasoline, with 24 recall campaigns attached. The first one listed, 19V182000, was filed in March 2019 against the driver's frontal airbag inflator. The row carries NHTSA's own summary of it, what the fault can lead to and the remedy the manufacturer offers, word for word.
You pay per decoded vehicle. A VIN that is malformed, or that the federal record doesn't know, comes back as a free row saying so.
What comes back for each VIN
| You want to know | Look at |
|---|---|
| What the vehicle is | make, model, modelYear, trim, bodyClass, vehicleType |
| Engine and drive | engineCylinders, displacementL, fuelTypePrimary, driveType, transmissionStyle |
| Where it was built | manufacturer, plantCountry, plantCity |
| Whether the recall look-up worked | recallLookup: ok, none when nothing is filed, unavailable when the look-up failed |
| The recalls themselves | recalls: campaign number, date, component, summary, consequence, remedy |
| A do-not-drive warning | parkIt and parkOutSide on each recall, NHTSA's own park-it and park-outside advisories |
A null usually means the manufacturer never filed that detail, not that the decode failed: the 2003 Accord has no driveType on record. nhtsaErrorText passes on the decoder's own warnings, and a code 1 about the check digit turns up on VINs that decode perfectly well.
When a VIN decoder is the wrong tool
- You're buying one car and want its past. Accidents, title brands, mileage and owners are in paid history reports, not in the factory record this reads.
- You need to know whether a recall was fixed on one particular car. NHTSA's own look-up on nhtsa.gov checks a single VIN for recall work still owed. The public data this tool reads stops at the model.
- The car was never sold in the US. There is no federal record to decode.
- The recall is for a medicine, a food or a medical device. That's the FDA recalls tool.
- It is not an official NHTSA tool. Dami's Studio is independent and is not affiliated with or endorsed by NHTSA, or by any other company named on this page.
How it works
- 1Open it on Apify
The Open on Apify button takes you there. Nothing to install.
- 2Set the inputs
The form opens with an example in VINs. Put in your own and check the other settings.
- 3Click Run
It runs on Apify's servers, on your own Apify account.
- 4Export the results
Download them from the run, or read them over Apify's API.
Pricing
$0.0009 per VIN = $0.90 per 1,000
Live price on Apify's Free plan, read on 5 November 2026. Paid plans pay a little less. You are billed on your own Apify account. The full price list is on the Apify page.
Use it from your AI chat
Add Apify's connector to your AI chat once (setup steps), then paste this:
Use the VIN Decoder & Recalls API (dami_studio/vin-decoder-recalls-scraper) to decode the VIN "1HGCM82633A004352" and list its open recalls, and return one row per decoded vehicle: specification, plant, safety equipment and its open recalls.Some apps ask for a server address instead. This one loads just this tool:
https://mcp.apify.com?tools=dami_studio/vin-decoder-recalls-scraperEvery run your AI chat starts goes on your own Apify account, at the prices on this tool's Apify page.
Questions people ask
Is this NHTSA's VIN decoder?
No. It reads the same public record NHTSA's decoder shows and hands it back as rows, up to 1,000 VINs at once, with the recall list for each model joined on.
Can I check recalls by VIN?
Yes, for the VIN's make, model and year: the campaigns filed for that model come back on its row. Whether the repair was already done on that exact car is not in the public data.
How many VINs can I decode at once?
Up to 1,000 a run. Duplicates are removed before any look-up starts, and recalls are fetched once per make, model and year, so a list of a few popular models finishes much faster than a thousand different ones.
Is there a VIN decoder API?
Yes. It runs from Apify's API like the other tools there: send the VINs as JSON and read the rows back as JSON or CSV. The API tab on its Apify page has the calls written out.
How much does VIN Decoder & Recalls API cost?
$0.0009 per VIN ($0.90 per 1,000) on Apify's Free plan. Paid plans pay a little less. It is billed on your own Apify account.
Can I run VIN Decoder & Recalls API from my AI chat?
Yes, from any app that supports MCP connectors. Add Apify's connector (https://mcp.apify.com/), sign in with your Apify account, and ask for dami_studio/vin-decoder-recalls-scraper. The steps are on the Use with AI page. Each run goes on your own Apify account, at the prices on its Apify page.
Do I need to write code to use VIN Decoder & Recalls API?
No. Open it on Apify, fill in the form, click Run and download the results.