← OLP Developer API

VIN-to-Specs Lookup API

Turn a year/make/model/engine into everything repairable about it: labor times, torque specs, fluid capacities, DTC context, and open recalls.

Get a free API key →Read the docs

Decoding a VIN is a solved problem — knowing what to DO with the vehicle isn't. Pair any VIN decoder (including free NHTSA vPIC) with OLP and the decoded vehicle becomes live repair data: what jobs exist, how long they take, which fluids and torque values apply, and what's under recall.

What you get

  • Vehicle-resolution endpoint: match make/model/year/engine strings to our 39,000-vehicle verified catalog
  • Then fan out: labor times, torque specs, fluid specs, battery specs, DTC codes, recalls — same key, same style
  • Catalog verified against automotive history: no phantom trims polluting your matches
  • Works with any VIN decoder upstream — we handle everything after the decode

One call, real data

curl -H "x-api-key: YOUR_KEY" \ "https://openlaborproject.com/api/v1/vehicles?make=toyota&model=tacoma&year=2019"
Response (abridged)
{ "data": [{ "make_name": "Toyota", "model_name": "Tacoma", "year_start": 2019, "year_end": 2019, "engine": "3.5L V6", "engine_slug": "3.5l-v6", "drivetrain": "4wd", "fuel_type": "gas" }] }

Built with this endpoint

Garage/vehicle-profile features in consumer appsShop check-in flows (VIN scan → full repair context)Used-car listing enrichmentInsurance claim triage

Pricing

Free — 7 requests/day, full read access, prototype tonight · Builder $49/mo — 1,000/day, 300/min, production-ready · Business $149/mo — 10,000/day, webhooks, bulk export, white-label · Enterprise — custom volume + SLA. Full comparison →

Common questions

Do you decode VINs directly?

Use NHTSA's free vPIC for the decode itself, then pass the decoded year/make/model/engine to OLP. This keeps your VIN pipeline free and adds the layer vPIC doesn't have: repair data.

How do I map decoded strings to your slugs?

The /vehicles endpoint accepts human-ish names and returns canonical slugs for all follow-up calls. Fuzzy-matching quirks? Email support and we'll tune it — matching quality is a priority.

What about vehicles older than VIN standardization (pre-1981)?

That's our specialty — the catalog runs back to 1955. Query by year/make/model directly; no VIN needed.

Key in your inbox within 30 minutes

Free tier, no card. Approval is automated — request now, be calling the API before your coffee cools.

Get your free key →
More API use cases
Labor Times APIAuto Repair Estimate APIVehicle Recalls APITorque Specs APICar Repair Data APIClassic Car Data APILabor Data for Shop Management PlatformsDVI-to-Estimate API