DVI-to-Estimate API
One call maps an inspection finding ("front brake pads, red") to the repair job, labor hours, parts with price ranges, and torque specs for that exact vehicle.
Digital vehicle inspections create findings; service writers still have to turn each one into an estimate line by hand. The DVI lookup collapses that: pass the inspection item and the vehicle (or just a VIN), get back the mapped repair job with labor hours, typical parts and retail ranges, and the relevant torque specs — everything an estimate line needs.
What you get
- Standard DVI/MPI taxonomy across 7 categories — under-hood, brakes, tires, steering/suspension, exhaust, electrical, driveline
- Forgiving matcher: mangled slugs, your own item names, and job slugs all resolve instead of 404ing
- Labor + parts + torque + fluid specs in a single response, scoped to the exact vehicle
- Drive it from a VIN: we decode make/model/year server-side
One call, real data
Built with this endpoint
Pricing
Common questions
Do I have to match your inspection taxonomy exactly?
No. The matcher accepts your item names, slugified variants, our job slugs, and known integrator spellings. If something genuinely can't resolve, the error lists every valid slug so your mapping layer can learn it once.
Where do the parts prices come from?
Typical retail ranges for the part class, marked with their own confidence. For vehicles where we carry real part numbers the response upgrades to database-backed parts with OEM numbers — the partsSource field tells you which you got.
Can this run inside a multi-tenant platform?
Yes — that's the primary use. Evaluation and small platforms run on the self-serve tiers; at scale, platform licensing applies (see /partners/).
Free tier, no card. Approval is automated — request now, be calling the API before your coffee cools.
Get your free key →