Recall data is public. It’s trapped behind a government site built for one VIN at a time.
Federal recall data is free and public — but the official interface is built for a consumer typing in a single VIN. If you need recall exposure across a fleet, or recalls mapped to year/make/model inside your app, you need structured data by API. That’s this.
Public data. A clean API.
We ingest federal recall campaigns, map them to the vehicles in our catalog, and serve them through one REST endpoint. A single call returns every recall on record for a vehicle — component, summary, consequence, and the manufacturer’s remedy — refreshed daily.
Affected-vehicle counts and fleet bulk lookup are on the roadmap.
What a recall response looks like.
Real records, structured. One call returns every recall on file for the vehicle.
{
"vehicle": "2008–2016 Toyota Land Cruiser",
"recalls": [
{
"campaign_id": "17V548000",
"component": "AIR BAGS: FRONTAL: PASSENGER SIDE: INFLATOR MODULE",
"summary": "Toyota is recalling certain Land Cruiser vehicles…",
"consequence": "An incorrect air bag may not deploy as intended in a crash…",
"remedy": "Dealers will replace the affected air bag assemblies, free of charge."
}
]
}Who needs recall data.
Fleet operators
You manage hundreds of vehicles, each with possible open recalls you don’t know about. Map your fleet’s recall exposure by year/make/model.
Insurance & claims
When a vehicle comes in with a reported issue, the first question is whether a recall covers it. Structured recall data at intake removes the manual lookup.
Shop management platforms
A service advisor pulls up a customer’s vehicle and sees open recalls before the conversation starts. That’s trust, in one API call.
Your users’ safety data shouldn’t be trapped on a government website.
Free tier. No credit card.