Documentation

PlateToVIN API

A single, predictable REST API for US vehicle data. Turn a license plate into a VIN, read a plate straight from a photo, decode a VIN into a full specification, check open safety recalls and the problems owners report, and serve catalog-grade vehicle images — all with plain HTTP and JSON. No SDK required.

Authentication

The JSON endpoints (License Plate to VIN and VIN Decoding) authenticate with an API key sent in the Authorization header. You can find your key on your API Keys page after signing in.

Keep your API key secret — send it only from your server. The Vehicle Images API uses a different, referer-based model that is safe for the browser (see Vehicle Images).
Authorization header
Authorization: sk_live_your_api_key_here

Base URL

All JSON endpoints live under a single HTTPS base. The Vehicle Images API is served from a dedicated image host.

JSON API
https://platetovin.com/api
Vehicle Images
https://vehicle-images.platetovin.com

Quickstart

Convert your first license plate to a VIN in one request. Replace the API key with your own, then switch languages on the right.

curl https://platetovin.com/api/convert \
  -H "Authorization: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{"state": "CA", "plate": "7ABC123"}'
const res = await fetch('https://platetovin.com/api/convert', {
  method: 'POST',
  headers: {
    'Authorization': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
    'Accept': 'application/json',
  },
  body: JSON.stringify({ state: 'CA', plate: '7ABC123' }),
});

const data = await res.json();
console.log(data.vin);
$res = Http::withHeaders(['Authorization' => 'YOUR_API_KEY'])
    ->acceptJson()
    ->post('https://platetovin.com/api/convert', [
        'state' => 'CA',
        'plate' => '7ABC123',
    ]);

$vin = $res->json('vin');
import requests

res = requests.post(
    'https://platetovin.com/api/convert',
    headers={'Authorization': 'YOUR_API_KEY', 'Accept': 'application/json'},
    json={'state': 'CA', 'plate': '7ABC123'},
)

print(res.json()['vin'])

License Plate to VIN

POST /api/convert

Convert a single US license plate and state into a VIN, along with a quick decode of the core vehicle attributes (make, model, year, trim, engine and more).

Body parameters

plate string required
The license plate characters, e.g. 7ABC123.
state string required
Two-letter US state code, e.g. CA, TX, NY.

Response fields

success boolean
Whether the lookup succeeded.
vin object
The matched VIN and a quick decode of the vehicle. For the full specification, pass the VIN to VIN Decoding.
vin string
The 17-character Vehicle Identification Number.
name string
Human-readable year / make / model, e.g. 2011 Mercedes-Benz M-Class.
year string
Model year.
make string
Manufacturer, e.g. Mercedes-Benz.
model string
Model name, e.g. M-Class.
trim string
Trim level, e.g. ML 350.
style string
Body style, e.g. SUV, Sedan.
engine string
Engine description, e.g. 3.5L V6 DOHC 24V.
fuel string
Fuel type, e.g. Gasoline.
driveType string
Drivetrain, e.g. AWD, FWD.
transmission string
Transmission type, e.g. Automatic.
GVWR integer|string
Gross vehicle weight rating in lbs. For vehicles with limited decode data this is the NHTSA GVWR class instead, e.g. Class 3: 10,001 - 14,000 lb. null when unavailable.
color object
The registered vehicle color, where known.
name string
Color name, e.g. Silver.
abbreviation string
State abbreviation code, e.g. SIL.
curl https://platetovin.com/api/convert \
  -H "Authorization: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"state": "CA", "plate": "7ABC123"}'
await fetch('https://platetovin.com/api/convert', {
  method: 'POST',
  headers: {
    'Authorization': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ state: 'CA', plate: '7ABC123' }),
});
200 — Response
{
  "success": true,
  "vin": {
    "vin": "4JGBB8GB9BA648907",
    "name": "2011 Mercedes-Benz M-Class",
    "year": "2011",
    "make": "Mercedes-Benz",
    "model": "M-Class",
    "trim": "ML 350",
    "style": "SUV",
    "engine": "3.5L V6 DOHC 24V",
    "fuel": "Gasoline",
    "driveType": "AWD",
    "transmission": "Automatic",
    "GVWR": 6063,
    "color": { "name": "Silver", "abbreviation": "SIL" }
  }
}

License Plate OCR

POST /api/ocr

Read a US license plate from a photo. We detect the plate in the scene (full photos are fine — no cropping needed), read the characters, correct them against the issuing state's plate format, and return the serial with a ranked list of candidate states, per-character confidences and the bounding box — everything you need to build your own capture or review flow. Uploaded images are never stored.

OCR never runs a VIN lookup by itself. When you want the VIN, take plate and state.code from a trusted read and call License Plate to VIN — and if that misses, retry with the next state_candidates entries, using each candidate's own plate value.

Check trusted before looking up. Blurry or uncertain reads come back as low_confidence with the best guess marked trusted: false — treat those as suggestions to confirm, not as input for a plate lookup.

Body parameters

image string | file required
The photo — JPEG or PNG, max 15 MB. Send either a base64 string (data: URIs accepted) in a JSON body, or a multipart file upload in the image field.
state_suggestions string[]
Ordered guesses for the issuing state, most likely first — e.g. ["NJ", "NY"] for a camera in New Jersey near the NY border. Strongly improves accuracy. It's a prior, not a filter: strong visual evidence for another state still wins. A comma-separated string ("NJ,NY") also works; unknown codes are ignored and echoed back in ignored_suggestions.

Statuses

ok status
The plate was read confidently — plate carries trusted: true and is safe to feed into License Plate to VIN.
low_confidence status
The characters couldn't be read reliably (blur, glare, angle). plate holds the best guess with trusted: false — treat it as a suggestion and re-shoot if you can.
no_plate_found status
The image was processed but no license plate was detected in it.
non_us_plate status
The plate is likely Canadian or Mexican. Only US jurisdictions (50 states, DC and territories) are supported.

Response fields

success boolean
Whether the call was processed.
status string
One of the statuses above.
request_id string
Correlation id for this OCR call — include it when contacting support about a read.
image object
Pixel dimensions of the processed image (width, height) — the coordinate space for bbox.
plate object
The best plate read. null when status is no_plate_found.
plate string
The read serial, separator-free and corrected against the state's plate format — the exact string to use for lookups.
plate_display string
The serial with the state's separators for display, e.g. ZZC-31V.
confidence float
Whole-string read confidence, 0–1.
char_confidences float[]
Per-character confidence, one entry per character of plate.
bbox int[]
Plate bounding box in image pixels: [x_min, y_min, x_max, y_max].
detection_confidence float
Confidence that the box contains a plate, 0–1.
state object
Most likely issuing jurisdiction.
code string
Two-letter code — 50 states, DC, or a US territory (PR, GU, VI, MP, AS).
name string
Full name, e.g. New Jersey.
confidence float
Probability across all jurisdictions, 0–1.
state_candidates object[]
Ranked alternative states (up to 5). Each carries its own plate — the serial as corrected under that state's format, occasionally differing by a character. When a plate lookup misses under the top state, retry with these, highest confidence first.
code · name · confidence mixed
Same shape as state.
plate string
The serial as it would read under this state's format.
plate_type string
passenger, commercial, motorcycle, … or vanity_or_unrecognized.
is_vanity_likely boolean
true when the plate looks personalized. Vanity plates are real registrations and still resolve to VINs.
warnings string[]
Why a read wasn't trusted, e.g. low_text_confidence, low_state_confidence, possibly_non_us_plate: <region>. Empty for clean reads.
trusted boolean
Whether the read is reliable enough to act on — e.g. to pass to License Plate to VIN.
additional_plates object[]
Other plates detected in multi-vehicle scenes, ordered by detection confidence, same shape as plate.
ignored_suggestions string[]
Entries from your state_suggestions that aren't valid jurisdiction codes.

Billing

Plans include a monthly OCR call allowance (unlimited on enterprise). Once it's used up, additional calls are billed per call from your account balance at your plan's overage rate — or refused with a 403 on plans without overage. Every processed image counts, whatever its status; rejected uploads and service errors don't. OCR itself never triggers a plate lookup — resolving a VIN through /api/convert is a separate call, billed as usual.

curl https://platetovin.com/api/ocr \
  -H "Authorization: YOUR_API_KEY" \
  -F "[email protected]" \
  -F "state_suggestions=NJ,NY"
curl https://platetovin.com/api/ocr \
  -H "Authorization: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "image": "'$(base64 -i driveway.jpg)'",
    "state_suggestions": ["NJ", "NY"]
  }'
const form = new FormData();
form.append('image', fileInput.files[0]);
form.append('state_suggestions', 'NJ,NY');

const res = await fetch('https://platetovin.com/api/ocr', {
  method: 'POST',
  headers: { 'Authorization': 'YOUR_API_KEY' },
  body: form,
});

const data = await res.json();
if (data.status === 'ok') {
  // Trusted read — resolve the VIN with /api/convert when you need it
  const { plate, state } = data.plate;
  console.log(plate, state.code);
}
200 — Response
{
  "success": true,
  "status": "ok",
  "request_id": "9e177840deec",
  "image": { "width": 3913, "height": 2678 },
  "plate": {
    "plate": "ZZC31V",
    "plate_display": "ZZC-31V",
    "confidence": 0.985,
    "char_confidences": [0.999, 0.999, 0.996, 0.996, 0.999, 0.995],
    "bbox": [2690, 1753, 3076, 2059],
    "detection_confidence": 0.91,
    "state": {
      "code": "NJ",
      "name": "New Jersey",
      "confidence": 0.98
    },
    "state_candidates": [
      { "code": "NJ", "name": "New Jersey", "confidence": 0.98, "plate": "ZZC31V" },
      { "code": "NY", "name": "New York", "confidence": 0.01, "plate": "ZZC31V" }
    ],
    "plate_type": "passenger",
    "is_vanity_likely": false,
    "warnings": [],
    "trusted": true
  }
}
200 — Low confidence
{
  "success": true,
  "status": "low_confidence",
  "request_id": "b41c09aa77f2",
  "image": { "width": 1920, "height": 1080 },
  "plate": {
    "plate": "8XK4O2",
    "plate_display": "8XK4O2",
    "confidence": 0.41,
    "char_confidences": [0.93, 0.88, 0.52, 0.61, 0.22, 0.35],
    "bbox": [811, 540, 1004, 634],
    "detection_confidence": 0.87,
    "state": { "code": "CA", "name": "California", "confidence": 0.44 },
    "state_candidates": [
      { "code": "CA", "name": "California", "confidence": 0.44, "plate": "8XK4O2" },
      { "code": "AZ", "name": "Arizona", "confidence": 0.21, "plate": "8XK402" }
    ],
    "plate_type": "passenger",
    "is_vanity_likely": false,
    "warnings": ["low_text_confidence", "low_state_confidence"],
    "trusted": false
  }
}

VIN Decoding

POST /api/vin-lookup

Decode a VIN into a complete vehicle specification: engine & drivetrain, performance, economy, dimensions, warranty, colors and standard/optional features. Requires a plan that includes VIN decoding.

Body parameters

vin string required
A 15–17 character VIN, e.g. WBAAV53431JR78115.

Response object groups

data contains the full specification. Depending on coverage for the vehicle, it may include the following nested objects — fields without data for a given vehicle are null:

year · make · model · trim · body_type string
Core vehicle identity.
trim_description · platform_code · domestic_import · manufacturer_country string
Extended identity details, where available — e.g. 330i Rwd 4dr Sedan (3.0L 6cyl 5M), E46, Imported, Germany.
msrp · base_invoice number
Original pricing information in USD, where available.
engine_drivetrain object
Engine and drivetrain specification.
cylinder_layout string
Cylinder configuration, e.g. I6, V8.
engine_displacement number
Displacement in litres.
engine_type string
e.g. gas, diesel, hybrid, electric.
fuel_type string
Required fuel, e.g. premium unleaded (required).
valves integer
Total valve count.
valve_timing string
e.g. Variable.
cam_type string
e.g. Double overhead cam (DOHC).
drivetrain string
e.g. rear wheel drive, all wheel drive.
transmission string
e.g. 5-speed manual, Automatic.
performance object
Factory performance figures.
horsepower integer
Peak horsepower.
horsepower_rpm integer
RPM at which peak horsepower is delivered.
torque integer
Peak torque in lb-ft.
torque_rpm integer
RPM at which peak torque is delivered.
zero_to_sixty_time number
0–60 mph time in seconds.
economy object
Fuel economy and range. EVs report range and miles/kWh equivalents.
fuel_tank_size number
Tank capacity in US gallons.
mpg_city integer
EPA city MPG.
mpg_highway integer
EPA highway MPG.
mpg_combined integer
EPA combined MPG.
range_city integer
City range in miles.
range_highway integer
Highway range in miles.
range_combined integer
Combined range in miles.
body object
Dimensions and weights.
gross_weight integer|string
Gross vehicle weight rating (GVWR) in lbs. For vehicles with limited decode data this is the NHTSA GVWR class instead, e.g. Class 3: 10,001 - 14,000 lb.
curb_weight integer
Curb weight in lbs.
length integer
Overall length in inches.
width integer
Overall width in inches.
height integer
Overall height in inches.
wheelbase integer
Wheelbase in inches.
ground_clearance number
Ground clearance in inches.
turning_circle number
Turning circle in feet.
doors integer
Door count.
seats integer
Seat count.
towing_capacity integer
Maximum towing capacity in lbs. null when the vehicle has no tow rating.
warranty object
Manufacturer warranty terms, e.g. 4 yr./ 50000 mi.
basic string
Basic (bumper-to-bumper) warranty.
drivetrain string
Drivetrain/powertrain warranty.
roadside string
Roadside assistance coverage.
rust string
Rust/corrosion warranty.
colors object
Factory color options with RGB values.
exterior object
Map of exterior color name → "R,G,B" value, e.g. "Jet Black": "0,0,0".
interior object
Map of interior color name → "R,G,B" value.
features object
Standard equipment grouped by category. Optional packages are included where the manufacturer provides them.
suspension string[]
Suspension features.
front_seats string[]
Front seating features and materials.
rear_seats string[]
Rear seating features.
features string[]
Convenience and comfort equipment.
safety string[]
Safety equipment, e.g. airbags, stability control, ABS.
curl https://platetovin.com/api/vin-lookup \
  -H "Authorization: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"vin": "WBAAV53431JR78115"}'
await fetch('https://platetovin.com/api/vin-lookup', {
  method: 'POST',
  headers: {
    'Authorization': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ vin: 'WBAAV53431JR78115' }),
});
200 — Response
{
  "success": true,
  "data": {
    "year": "2001",
    "make": "BMW",
    "model": "3 Series",
    "trim": "330i - Sedan",
    "trim_description": "330i Rwd 4dr Sedan (3.0L 6cyl 5M)",
    "body_type": "Sedan",
    "msrp": 33990,
    "base_invoice": 30750,
    "domestic_import": "Imported",
    "manufacturer_country": "Germany",
    "platform_code": "E46",
    "engine_drivetrain": {
      "cylinder_layout": "I6",
      "engine_displacement": 3,
      "engine_type": "gas",
      "fuel_type": "premium unleaded (required)",
      "valves": 24,
      "valve_timing": "Variable",
      "cam_type": "Double overhead cam (DOHC)",
      "drivetrain": "rear wheel drive",
      "transmission": "5-speed manual"
    },
    "performance": {
      "horsepower": 225,
      "horsepower_rpm": 5900,
      "torque": 214,
      "torque_rpm": 3500,
      "zero_to_sixty_time": 4.76
    },
    "economy": {
      "fuel_tank_size": 16.6,
      "mpg_city": 18,
      "mpg_highway": 27,
      "mpg_combined": 22,
      "range_city": 298,
      "range_highway": 448,
      "range_combined": 366
    },
    "body": {
      "gross_weight": 3931,
      "curb_weight": 3318,
      "length": 176,
      "width": 68,
      "height": 55,
      "wheelbase": 107,
      "ground_clearance": null,
      "turning_circle": 34,
      "doors": null,
      "seats": 5,
      "towing_capacity": 1000
    },
    "warranty": {
      "basic": "4 yr./ 50000 mi.",
      "drivetrain": "4 yr./ 50000 mi.",
      "roadside": null,
      "rust": null
    },
    "colors": {
      "exterior": {
        "Steel Gray Metallic": "60,60,65",
        "Orient Blue Metallic": "30,94,130",
        "Jet Black": "0,0,0",
        "Alpine White": "255,255,255",
        "Bright Red": "159,14,5",
        "Titanium Silver Metallic": "171,172,175"
      },
      "interior": {
        "Sand": "191,147,98",
        "Gray": "134,143,142",
        "Black": "0,0,0"
      }
    },
    "features": {
      "suspension": ["Four-wheel independent suspension"],
      "front_seats": ["Bucket front seats", "Vinyl"],
      "rear_seats": ["Split-folding rear seatback"],
      "features": [
        "1 one-touch power windows",
        "Remote keyless power door locks",
        "Heated mirrors",
        "Power mirrors"
      ],
      "safety": [
        "Child seat anchors",
        "Daytime running lights",
        "Dual front side-mounted airbags",
        "Engine immobilizer",
        "Stability control",
        "Traction control",
        "4-wheel ABS"
      ]
    }
  }
}

Safety Recalls

POST /api/recalls

Look up open NHTSA safety recall campaigns for a vehicle. Send a VIN and we decode it in-house, then return every recall campaign filed for that year, make and model — newest first. You can also query by year, make and model directly.

Recall lookups are free per call on plans that include them — they never consume credit and have no monthly cap.

Recall campaigns apply to a vehicle configuration (year / make / model), not to an individual VIN. Whether a specific VIN has already had a recall remedied is manufacturer-held data and is not included.

Body parameters

vin string required
A 15–17 character VIN, e.g. 1FTFW1ED0MFA63198. Not required when make, model and year are supplied instead.
make string
Vehicle make, e.g. Ford. Required together with model and year when vin is omitted.
model string
Vehicle model, e.g. F-150. Required together with make and year when vin is omitted.
year integer
Model year, e.g. 2021. Required together with make and model when vin is omitted.

Response fields

success boolean
Whether the lookup succeeded.
data object
The resolved vehicle and its recall campaigns.
vin string
The VIN you supplied, or null when querying by make/model/year.
year · make · model string
The vehicle the recalls apply to.
count integer
Number of recall campaigns. 0 with an empty recalls array means no recalls on file.
recalls object[]
Recall campaigns, newest first.
campaign_number string
NHTSA campaign number, e.g. 22V412000.
report_date string
Date NHTSA received the recall report, YYYY-MM-DD.
component string
Affected component, e.g. SEAT BELTS.
summary string
What is wrong with the vehicle.
consequence string
The safety risk if left unrepaired.
remedy string
How the manufacturer will fix it (recall repairs are free to the owner).
notes string
Additional notes from NHTSA.
manufacturer string
Filing manufacturer, e.g. Ford Motor Company.
park_it boolean
true when NHTSA advises the vehicle should not be driven.
park_outside boolean
true when NHTSA advises parking outdoors due to fire risk.
over_the_air_update boolean
true when the remedy is delivered as an over-the-air update.
curl https://platetovin.com/api/recalls \
  -H "Authorization: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"vin": "1FTFW1ED0MFA63198"}'
await fetch('https://platetovin.com/api/recalls', {
  method: 'POST',
  headers: {
    'Authorization': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ vin: '1FTFW1ED0MFA63198' }),
});
200 — Response
{
  "success": true,
  "data": {
    "vin": "1FTFW1ED0MFA63198",
    "year": 2021,
    "make": "Ford",
    "model": "F-150",
    "count": 2,
    "recalls": [
      {
        "campaign_number": "22V412000",
        "report_date": "2022-06-08",
        "component": "SEAT BELTS",
        "summary": "Ford Motor Company (Ford) is recalling certain 2021 F-150 vehicles. The front seat belt buckle assembly may be improperly secured.",
        "consequence": "A seat belt that does not properly restrain the occupant increases the risk of injury in a crash.",
        "remedy": "Dealers will inspect and replace the seat belt buckle assembly as necessary, free of charge.",
        "notes": "Owners may also contact the NHTSA Vehicle Safety Hotline at 1-888-327-4236.",
        "manufacturer": "Ford Motor Company",
        "park_it": false,
        "park_outside": false,
        "over_the_air_update": false
      },
      {
        "campaign_number": "21V576000",
        "report_date": "2021-07-28",
        "component": "ELECTRICAL SYSTEM",
        "summary": "...",
        "consequence": "...",
        "remedy": "...",
        "notes": "...",
        "manufacturer": "Ford Motor Company",
        "park_it": false,
        "park_outside": false,
        "over_the_air_update": true
      }
    ]
  }
}

Vehicle Issues

POST /api/vehicle-issues

What to look out for on a used car at its mileage — ready to drop into a vehicle history report, inspection checklist or underwriting screen. We group every owner complaint filed with NHTSA into named problems per make and model, learn the mileage each one is usually reported at, and sort this vehicle's problems into four lists:

  • watch_now — commonly reported around this mileage.
  • coming_up — usually reported later, soonest first.
  • check_was_fixed — usually reported earlier in the car's life: ask whether it was dealt with. Problems the manufacturer issued a fix for come first.
  • any_mileage — no clear mileage pattern.

Every problem comes with plain-English what_to_check (what an inspector or buyer can look for) and ask_the_seller (the question to ask, naming the manufacturer's bulletin or warranty extension where there is one), plus a headline paragraph summarising the lot. Send the odometer reading as mileage; without it we estimate from the vehicle's age.

Send a VIN for the most precise answer: we match complaints from vehicles with the same model line, body and engine (VIN positions 4–8) and model year, and fall back to the whole model year when that trim has too few reports. You can also query by year, make and model. Vehicle issue lookups are free and unlimited on plans that include them.

Issues are built from owner-reported complaints. NHTSA does not verify them, and a reported issue is not a confirmed defect — present it to your users as "owners report". Data is rebuilt weekly; data_through is the date of the newest complaint included.

Guidance text (title, what_to_check, ask_the_seller, manufacturer_fix.summary) is written by an AI model from the complaints and the manufacturer's own communications. Check the linked documents before relying on a specific bulletin number.

vs_similar_vehicles uses vehicles-on-the-road counts from Washington State Department of Licensing registration data, made available under the Open Database License.

Body parameters

vin string required
A 17-character VIN, e.g. 2HKRW2H86HH123456. Not required when make, model and year are supplied instead.
make string
Vehicle make, e.g. Honda. Required together with model and year when vin is omitted.
model string
Vehicle model, e.g. CR-V. Required together with make and year when vin is omitted.
year integer
Model year, e.g. 2017. Required together with make and model when vin is omitted.
mileage integer
The odometer reading, e.g. 72000. Decides which list each problem lands in. When omitted we estimate it from the model year (12,000 miles a year) and say so in mileage.source.
level string
trim (default with a VIN) or year to count every complaint for the model year. Year/make/model queries are always answered at year level.
limit integer
Maximum problems returned in each list. Default 10, maximum 50.

Response fields

success boolean
Whether the lookup succeeded.
data object
The resolved vehicle and what to look out for.
vehicle object
vin, year, make, model, and — for VIN lookups — the decoded trim and engine.
level string
trim or year: which complaints the counts are drawn from. A VIN falls back to year when its trim has fewer than 10 reports.
data_through string
Date of the newest complaint in the data, YYYY-MM-DD.
mileage object
value used to sort the lists and its source: provided or estimated.
headline string
A short paragraph summarising the lists, ready to show as-is: what to watch for now, what comes next, and what to check was fixed.
summary object
issues and owner_reports across every problem, how many are safety_related, and how many are in each list. Counts include problems beyond limit.
watch_now object[]
Problems commonly reported around this mileage, most reported first.
coming_up object[]
Problems usually reported later, soonest first.
check_was_fixed object[]
Problems usually reported earlier in the car's life. Those with a manufacturer fix come first.
any_mileage object[]
Problems with no clear mileage pattern (too few mileages, or reported across a wide range). Each list holds problem objects:
id string
Stable problem id, e.g. honda-cr-v-engine-oil-2. Unchanged between weekly rebuilds.
title string
The problem in plain English, as an owner would describe it.
short_name string
A lowercase phrase that reads after "watch for", e.g. fuel in the engine oil.
summary string
One or two sentences on the symptoms, starting "Owners report". May be null for a newly found problem.
category object
One of 33 standard categories (id, name, group), identical across every vehicle. vs_similar_vehicles: this model year's complaint rate in the category against every vehicle of the same model year, per vehicle on the road — 1.0 is average, 3.0 three times average, null when there are too few registrations to rate.
safety_related boolean
The problem affects braking, steering, stalling, airbags, visibility or fire risk, or reports involve crashes, fires or injuries.
owner_reports object
Complaints from matching_vehicles (at level), the whole model_year, and all_years of the model.
reported_at object
Odometer readings when owners report it, across all model years: from (25th percentile), median, to (75th percentile), sample_size. null when there is no clear pattern. Owners report most while a car is new, so read this as when problems are reported, not a failure rate.
what_to_check string
What a buyer or inspector can check on the car: what to look at, listen for or try on a test drive, or a fault code to scan for.
ask_the_seller string
The question to ask the seller or look for in service records — naming the manufacturer's bulletin, software update or warranty extension where there is one.
manufacturer_fix object
What the manufacturer has published for this model year. status: warranty_extension, fix_available, investigating, acknowledged or none. summary: one sentence on the remedy, or null. documents: up to 3 matching communications, each with type (warranty_extension, service_bulletin, software_update, service_campaign, owner_letter, dealer_message, other), the manufacturer's id, date, title and an NHTSA url.
severity object
Reports involving crashes, fires, injuries and deaths.
merged_issues string[]
Ids of smaller problems folded into this one because owners describe the same thing in different ways.
evidence object
nhtsa_complaints: up to 5 of the most recent NHTSA complaint (ODI) numbers behind it.
curl https://platetovin.com/api/vehicle-issues \
  -H "Authorization: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"vin": "2HKRW2H86HH123456", "mileage": 72000, "limit": 1}'
await fetch('https://platetovin.com/api/vehicle-issues', {
  method: 'POST',
  headers: {
    'Authorization': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ vin: '2HKRW2H86HH123456', mileage: 72000, limit: 1 }),
});
curl https://platetovin.com/api/vehicle-issues \
  -H "Authorization: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"year": 2017, "make": "Honda", "model": "CR-V", "mileage": 72000, "limit": 5}'
200 — Response (limit 1)
{
  "success": true,
  "data": {
    "vehicle": {
      "vin": "2HKRW2H86HH123456",
      "year": 2017,
      "make": "Honda",
      "model": "CR-V",
      "trim": "EX-L/EX-L Navi",
      "engine": "1.5L 4-cyl gasoline"
    },
    "level": "trim",
    "data_through": "2026-10-26",
    "mileage": {
      "value": 72000,
      "source": "provided"
    },
    "headline": "At 72,000 miles, owners of the 2017 Honda CR-V most often report fuel injector failure, fuel pump failure and cold start rattle around this point. Coming up: head gasket failure, usually reported from about 73,000 miles. Earlier in its life it was known for phantom automatic braking and fuel in the engine oil, which the manufacturer issued fixes for: ask for proof the work was done. At any mileage, owners also report engine stalling.",
    "summary": {
      "issues": 22,
      "owner_reports": 437,
      "safety_related": 8,
      "watch_now": 3,
      "coming_up": 1,
      "check_was_fixed": 12,
      "any_mileage": 6
    },
    "watch_now": [
      {
        "id": "honda-cr-v-fuel-system-2",
        "title": "Dashboard warning lights and hard starting from fuel injector failure",
        "short_name": "fuel injector failure",
        "summary": "Owners report multiple dashboard warning lights appearing, sometimes intermittently, along with difficulty starting, no-start, or stumbling. The check engine light may come on with a low fuel pressure code.",
        "category": {
          "id": "fuel_system",
          "name": "Fuel system",
          "group": "powertrain",
          "vs_similar_vehicles": 5.88
        },
        "safety_related": false,
        "owner_reports": {
          "matching_vehicles": 29,
          "model_year": 101,
          "all_years": 253
        },
        "reported_at": {
          "from": 50500,
          "median": 65238,
          "to": 89826,
          "sample_size": 119
        },
        "what_to_check": "Check for stored diagnostic trouble code P0087 (fuel rail pressure too low). On a test drive, note if the engine is hard to start or stumbles. Listen for unusual engine behavior.",
        "ask_the_seller": "Have the fuel injectors been replaced, and if so, was the repair covered under any warranty or goodwill program?",
        "manufacturer_fix": {
          "status": "none",
          "summary": null,
          "documents": []
        },
        "severity": {
          "crashes": 0,
          "fires": 0,
          "injuries": 0,
          "deaths": 0
        },
        "merged_issues": [],
        "evidence": {
          "nhtsa_complaints": [
            "11750874",
            "11750613",
            "11740681",
            "11730570",
            "11725617"
          ]
        }
      }
    ],
    "coming_up": [
      {
        "id": "honda-cr-v-engine-cooling",
        "title": "Engine overheats, loses coolant, and misfires",
        "short_name": "head gasket failure",
        "summary": "Owners report sudden overheating, coolant loss, and rough running or misfires. The temperature gauge may spike and coolant disappears without visible leaks.",
        "category": {
          "id": "engine_cooling",
          "name": "Cooling system and overheating",
          "group": "powertrain",
          "vs_similar_vehicles": 0.22
        },
        "safety_related": false,
        "owner_reports": {
          "matching_vehicles": 6,
          "model_year": 22,
          "all_years": 84
        },
        "reported_at": {
          "from": 72550,
          "median": 89000,
          "to": 111322,
          "sample_size": 47
        },
        "what_to_check": "Check coolant level and condition; look for white smoke from exhaust or milky oil on dipstick. On a test drive, monitor temperature gauge for erratic behavior and listen for rough idle or misfire.",
        "ask_the_seller": "Ask if the cylinder head gasket was replaced under Service Bulletin A26-016 and if the repair included the updated gasket and any related software update.",
        "manufacturer_fix": {
          "status": "fix_available",
          "summary": "Honda Service Bulletin A26-016 describes replacing the cylinder head gasket with an improved part to address reduced gasket effectiveness that can cause overheating, coolant loss, and misfire.",
          "documents": [
            {
              "type": "service_bulletin",
              "id": "A26-016",
              "date": "2026-09-25",
              "title": "Under certain conditions, the cylinder head gasket effectiveness may be reduced which may cause vehicles to experience overheating, coolant loss, and/or misfire.",
              "url": "https://www.nhtsa.gov/vehicle/manufacturer-communications?nhtsaId=11037702"
            },
            {
              "type": "dealer_message",
              "id": "AEBM08262026901",
              "date": "2026-08-26",
              "title": "Under certain conditions, the cylinder head gasket effectiveness may be reduced which may cause vehicles to experience overheating, coolant loss, misfire, and/or DTCs P0300 through P0304 stored.",
              "url": "https://www.nhtsa.gov/vehicle/manufacturer-communications?nhtsaId=11036424"
            },
            {
              "type": "service_bulletin",
              "id": "A26-016",
              "date": "2026-08-26",
              "title": "Under certain conditions, the cylinder head gasket effectiveness may be reduced which may cause vehicles to experience overheating, coolant loss, misfire and/or DTCs P0300 thru P0304 stored.",
              "url": "https://www.nhtsa.gov/vehicle/manufacturer-communications?nhtsaId=11036413"
            }
          ]
        },
        "severity": {
          "crashes": 0,
          "fires": 0,
          "injuries": 0,
          "deaths": 0
        },
        "merged_issues": [],
        "evidence": {
          "nhtsa_complaints": [
            "11753636",
            "11730975",
            "11729121",
            "11659391",
            "11656996"
          ]
        }
      }
    ],
    "check_was_fixed": [
      {
        "id": "honda-cr-v-park-shifter",
        "title": "Shift knob button breaks and pops out",
        "short_name": "broken shift button",
        "summary": "Owners report the shift knob button breaking and popping out, often while shifting into or out of park. This can make it difficult or impossible to move the gear selector.",
        "category": {
          "id": "park_shifter",
          "name": "Park, shifter and rollaway",
          "group": "powertrain",
          "vs_similar_vehicles": 2.06
        },
        "safety_related": true,
        "owner_reports": {
          "matching_vehicles": 42,
          "model_year": 156,
          "all_years": 179
        },
        "reported_at": {
          "from": 12750,
          "median": 22806,
          "to": 36250,
          "sample_size": 136
        },
        "what_to_check": "Check the shift knob button for cracks or looseness. Try pressing it firmly while shifting; if it feels brittle or moves abnormally, it may be failing.",
        "ask_the_seller": "Ask if the product update for the shift knob button (referenced in owner notification letters) has been completed.",
        "manufacturer_fix": {
          "status": "fix_available",
          "summary": "Honda issued a product update to replace the shift knob with a revised part made of a different material that is less susceptible to breakage from heat and humidity.",
          "documents": [
            {
              "type": "owner_letter",
              "id": "ONL6DK07232019",
              "date": "2019-07-23",
              "title": "On some CR-V models, the material that the shift button is made of is susceptible to heat and humidity and may break.",
              "url": "https://www.nhtsa.gov/vehicle/manufacturer-communications?nhtsaId=10163451"
            },
            {
              "type": "service_bulletin",
              "id": "A19-063",
              "date": "2019-05-29",
              "title": "The shift knob button is susceptible to breakage after being exposed to heat and humidity.",
              "url": "https://www.nhtsa.gov/vehicle/manufacturer-communications?nhtsaId=10160912"
            },
            {
              "type": "owner_letter",
              "id": "ONLE5007192021",
              "date": "2021-07-19",
              "title": "Our records indicate that a PRODUCT UPDATE has not been completed on this vehicle (Vehicle Identification Number XXXXXXXXXXXXXXXXX).",
              "url": "https://www.nhtsa.gov/vehicle/manufacturer-communications?nhtsaId=10199468"
            }
          ]
        },
        "severity": {
          "crashes": 0,
          "fires": 0,
          "injuries": 0,
          "deaths": 0
        },
        "merged_issues": [
          "honda-cr-v-seats-interior-2"
        ],
        "evidence": {
          "nhtsa_complaints": [
            "11551328",
            "11493449",
            "11484907",
            "11474998",
            "11468845"
          ]
        }
      }
    ],
    "any_mileage": [
      {
        "id": "honda-cr-v-engine-stall-power",
        "title": "Engine stalls without warning while driving",
        "short_name": "engine stalling",
        "summary": "Owners report the engine suddenly stalls or loses power while driving at various speeds, including on the highway and at stoplights. The failure occurs without warning and may be intermittent, sometimes restarting after pressing the accelerator.",
        "category": {
          "id": "engine_stall_power",
          "name": "Stalling or loss of power",
          "group": "powertrain",
          "vs_similar_vehicles": 0.74
        },
        "safety_related": true,
        "owner_reports": {
          "matching_vehicles": 17,
          "model_year": 79,
          "all_years": 545
        },
        "reported_at": null,
        "what_to_check": "On a test drive, accelerate from a stop and at highway speeds to see if the engine hesitates, loses power, or stalls. Check for any stored diagnostic trouble codes with an OBD-II scanner.",
        "ask_the_seller": "Ask if the stalling issue has ever occurred and whether any repairs or diagnostic work were performed.",
        "manufacturer_fix": {
          "status": "fix_available",
          "summary": null,
          "documents": [
            {
              "type": "owner_letter",
              "id": "CL_6DU_12172018",
              "date": "2018-12-17",
              "title": "On 2017-18 CR-V vehicles equipped with the 1.5 liter turbocharged engine, there are reports of vehicles experiencing drivability concerns.",
              "url": "https://www.nhtsa.gov/vehicle/manufacturer-communications?nhtsaId=10152444"
            },
            {
              "type": "service_bulletin",
              "id": "ONL6DU02102020",
              "date": "2020-02-10",
              "title": "Followup Notice - Our records indicate that a PRODUCT UPDATE has not been completed on this vehicle; refer to the address card for the affected VIN.",
              "url": "https://www.nhtsa.gov/vehicle/manufacturer-communications?nhtsaId=10171554"
            },
            {
              "type": "dealer_message",
              "id": "ATI&08262024902",
              "date": "2024-08-26",
              "title": "American Honda Motor Co., Inc. (AHM) is searching for certain 2018-2022 Accord FHEVs, as well as 2017-2022 CR-V 1.5Ls (no 2.4L), & 2020-2022 CR-V FHEVs with a customer complaint of the Malfunction…",
              "url": "https://www.nhtsa.gov/vehicle/manufacturer-communications?nhtsaId=11006807"
            }
          ]
        },
        "severity": {
          "crashes": 0,
          "fires": 0,
          "injuries": 0,
          "deaths": 0
        },
        "merged_issues": [
          "honda-cr-v-turbo",
          "honda-cr-v-hybrid-ev-battery",
          "honda-cr-v-engine-stall-power-2"
        ],
        "evidence": {
          "nhtsa_complaints": [
            "11755149",
            "11749795",
            "11744566",
            "11618994",
            "11579535"
          ]
        }
      }
    ]
  }
}

Vehicle Images

GET vehicle-images.platetovin.com/image

Serve catalog-grade vehicle images straight from an <img> tag. Every image is a transparent PNG rendered at a fixed, consistent framing so vehicles line up perfectly across a page. Five angles, six colors, three sizes — all from one HTTP GET.

Referer-based auth. Instead of an API key, the image API authorizes requests by the Referer of the whitelisted domains on your account. Add your domains in your dashboard, then hotlink the URLs directly.
Image licensing — read this. Without a licence (including unauthenticated requests), images are served as small, watermarked previews for evaluation only. Full-resolution, watermark-free images require an active plan with vehicle images enabled — with it, you may hotlink via the API or download and self-host the images for use in your own applications and listings. When your licence ends, you must stop using and delete any downloaded images. Reselling or redistributing images as standalone assets, and removing or bypassing watermarks, is never permitted. We use automated systems to detect unlicensed use of our imagery and may request proof of licence; unlicensed use can lead to suspension and legal action. Full details in the Terms of Service, Section 2.3.
Try it free, no key. Add tier=free to any request for the public watermarked preview — front angle, low-resolution, no referer or key required — or browse and download previews from the image library. A vehicle without a generated preview returns 404.

Query parameters

search string required
Make and model, e.g. BMW 3 Series. Matching resolves make, model and generation server-side.
year integer required
Model year, e.g. 2022. Years newer than our latest imagery fall back to the closest available model year, so current-generation vehicles always render.
angle string
One of front, front_angle, side, rear, rear_angle. Defaults to front_angle.
color string
One of base, silver, black, white, gray, red. Defaults to base.
size string
One of large, medium, small. Defaults to large.
tier string
Set to free for the public, no-auth watermarked preview — front angle only, low-resolution, with a forced background. All other parameters are ignored; a vehicle without a generated preview returns 404. Omit for licensed full-resolution images.

Want the full walkthrough with a live playground? See the Vehicle Images page →

Drop straight into HTML
<img
  src="https://vehicle-images.platetovin.com/image?search=BMW+3+Series&year=2022&angle=front_angle&color=red"
  alt="2022 BMW 3 Series"
/>
rendered result
2022 BMW 3 Series

Errors

The JSON API returns a consistent shape on failure — success: false with a human-readable message — alongside a standard HTTP status code.

Status Meaning
200 Success. Note: validation failures may also return 200 with success: false — always check the success flag.
402 Payment required — your account balance is too low to run the lookup. Top up or enable auto-deposit.
403 Forbidden — no billing plan assigned, the account is suspended, your plan doesn't include this endpoint (e.g. VIN decoding), or a monthly limit was reached on a plan without overage.
404 No result found for the supplied plate or VIN.
413 The uploaded image exceeds the 15 MB limit (OCR). Downscale or re-encode it.
422 The upload couldn't be decoded as an image (OCR).
503 The service behind this endpoint is temporarily unavailable — safe to retry shortly.
Error response
{
  "success": false,
  "message": "Not enough credit"
}

Billing & limits

API access requires an active billing plan. License plate lookups are billed per request and cached for seven days — repeated lookups of the same plate within that window are free. VIN decoding and vehicle images are included on the plans that offer them, up to any monthly ceiling on your tier. Safety recall lookups are free per call on plans that include them — no credit charge and no monthly cap. Vehicle issue lookups are free and unlimited on the plans that include them (Enterprise).

License plate OCR comes with a monthly call allowance per plan (unlimited on enterprise). Past the allowance, calls are billed individually from your balance at your plan's overage rate; plans without an overage rate pause OCR until the allowance resets. OCR never runs a plate lookup itself — resolving a read to a VIN is a separate /api/convert call, billed as usual.

Ready to build?

Pick a plan or create an account to get your API key.