Vehicle Recalls API
Open NHTSA safety recalls for any US vehicle, queried the same way you query everything else about it.
Recall checks belong in every intake flow — dealership check-ins, used-car listings, fleet audits, insurance quotes. NHTSA publishes the data but querying it per-vehicle alongside repair data means stitching two systems. OLP serves recalls in the same API as labor, specs, and fluids: one key, one style, one call per vehicle.
What you get
- NHTSA recall campaigns matched to our verified vehicle catalog
- Component, summary, consequence, and remedy text — ready to render
- Variant-aware matching (a Camaro SS correctly inherits base-Camaro recalls)
- Combine with labor times: show the recall AND what the related repair involves
One call, real data
Built with this endpoint
Pricing
Common questions
How fresh is the recall data?
Ingested from NHTSA's published dataset on a recurring schedule. For legal-compliance-critical flows, treat NHTSA.gov as the system of record and OLP as the integration layer.
Do you cover recalls for older vehicles?
We serve what NHTSA publishes, matched against our 1955-present catalog — older campaigns exist in the data and match where NHTSA recorded them.
Can I get recalls and repair data in one integration?
That's the whole point — same API key and conventions across recalls, labor times, torque, fluids, batteries, and DTC codes.
Free tier, no card. Approval is automated — request now, be calling the API before your coffee cools.
Get your free key →