Skip to content

VIN decoder API for year, make, model and engine

Send a 17-character VIN and get the vehicle's specification from NHTSA vPIC: year, make, model, trim, body class, engine, fuel type, drive type and assembly plant, plus a check-digit result. 2 credits per lookup.

2 creditsEnrichCSV bulkMCP
POST/v1/vin-decoder
{
  "success": true,
  "data": {
    "vin": "1HGCM82633A004352",
    "check_digit_valid": true,
    "year": 2003,
    "make": "Honda",
    "model": "Accord",
    "trim": "EX-V6",
    "vehicle_type": "passenger_car",
    "body_class": "Coupe",
    "doors": 2,
    "engine": {
      "cylinders": 6,
      "displacement_l": 3,
      "model": "J30A4"
    },
    "fuel_type": "gasoline",
    "drive_type": "fwd",
    "plant": {
      "city": "Marysville",
      "state": "Ohio",
      "country": "United States"
    }
  },
  "meta": {
    "credits_used": 2,
    "credits_remaining": 999,
    "cached": false,
    "request_id": "req_8f3a2c1e9b7d"
  }
}
[01/Response]

What you get back

The fields most teams branch on. The full response is in the sample on this page and in the API reference.

check_digit_validCheck digitWhether the ninth character matches the value computed from the rest of the VIN.
yearModel yearThe model year encoded in the VIN.
makeMakeThe vehicle brand.
modelModelThe model name, returned with trim where the manufacturer reports it.
body_classBody classThe body style, such as coupe, sedan, pickup or SUV.
engineEngineCylinders, displacement and engine model.
fuel_typeFuel typeThe primary fuel, such as gasoline, diesel or electric.
plantAssembly plantThe city and country where the vehicle was built.
[02/Capabilities]

What VIN Decoder does

01

Year, make, model and trim

The decode turns 17 characters into the fields people recognize. Fill them in for the user instead of asking them to pick from four dropdowns.

02

Engine, fuel and drivetrain

Cylinders, displacement, fuel type and drive type come back where the manufacturer reported them. Parts lookups and service estimates depend on exactly these details.

03

Body class and vehicle type

The response separates passenger cars from trucks, motorcycles, buses and trailers, and gives the body class within each. A pickup and a sedan from the same brand are not confused.

04

Check-digit validation

The ninth character of a North American VIN is a check digit computed from the other sixteen. The response tells you whether it is correct, which catches most typing errors before they reach your database.

[03/Try it]

See the response before you sign up

Fill in the request and run it. The dashboard has the same form, plus history, bulk upload and live data.

POST /v1/vin-decoder2 credits

Preview mode: this page returns a sample response so you can see the shape of the data. Create a key to run it on live data.

Response

Fill in the field and run the lookup to see what comes back.

[04/Integrate]

One POST request

Send JSON with a Bearer key. The same key works for all 79 products.

curl -X POST https://api.1lookup.dev/v1/vin-decoder \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"vin":"1HGCM82633A004352"}'
Endpoint
POST /v1/vin-decoder
Base URL
https://api.1lookup.dev
Request
vin
Price
2 credits
Coverage
Vehicles sold in North America since 1981
Source
NHTSA vPIC
Bulk
CSV upload and bulk API
Cache
Repeats within 7 days are free
Also via
Dashboard and MCP server (run_lookup)
[05/Use cases]

What teams use it for

Prefill vehicle details on a form

Marketplaces, lenders and service schedulers ask for the VIN and fill in year, make and model, so the user confirms instead of typing.

Normalize dealer and fleet inventory

Upload an inventory file as a CSV and get consistent year, make, model and body fields for every row, whatever the source system called them.

Reject bad VINs at intake

Use the check-digit result to stop a mistyped VIN at the form, before it creates a work order or a title application that has to be corrected later.

Match parts and service to the vehicle

Repair shops and parts sellers use engine and body details to show only the items that fit.

Covers 17-character VINs for vehicles sold in North America since model year 1981. The decode describes the vehicle as built and does not include ownership, accident or title history.

[06/Cost]

2 credits

Credits come with your plan and work on every product. Requests that fail on our side are never charged. Beyond your plan, extra credits are pay as you go.

See pricing
PlanPer 1,000 creditsPer 1,000 lookups
Starter $29/mo$4.83$9.67
Growth $99/mo$3.96$7.92
Pro $299/mo$3.32$6.64
Scale $799/mo$2.66$5.33
[07/FAQ]

VIN Decoder questions

Does it include accident, title or ownership history?

No. vPIC describes how the vehicle was built. It holds nothing about owners, accidents, odometer readings, liens or title brands. This product does not provide a vehicle history report.

Which vehicles can it decode?

Vehicles built for sale in North America from model year 1981 onward, when the 17-character VIN format became standard. Older vehicles with shorter VINs and vehicles built only for other markets may not decode, or may return partial data.

How much does decoding a VIN cost?

2 credits per VIN. Decoding the same VIN again within 7 days is free, which helps when one vehicle passes through several steps of your workflow.

Where does the decode come from, and does it include new model years?

It comes from vPIC, the Product Information Catalog that NHTSA builds from what manufacturers are required to submit about their VINs. New model years appear as manufacturers file them, and our data follows NHTSA's publication schedule.

Why are some fields empty?

vPIC only contains what the manufacturer encoded in the VIN and reported to NHTSA. Details such as trim or drive type are not captured for every make and year, so those fields come back null when the source has nothing.

[ Validate ][ Enrich ]
[Get started]

Run VIN Decoder on your own data

Starter is $29 a month for 6,000 credits, enough for 3,000 lookups a month.

[ Screen ][ Scrape ]