VIN Decoder API, Built for Parts
Send a VIN or plate number and AutoWiz tells you which parts from your own stock are a perfect fit — not just the vehicle's make, model, and trim.
Request a pilot on your inventoryVIN to verified part
Most VIN decoders stop once they've told you the vehicle's specification. AutoWiz takes that decode one step further: it cross-references the vehicle against your own inventory and returns the parts that are actually a verified fit, ready to quote or add to cart.
That second step is where parts businesses lose time. Two cars with the same make, model and year can take different filters, brake parts or belts because of an engine code or a mid-year change. The decoded engine model and capacity are what separate them, and AutoWiz uses them to pick the right OEM numbers so your staff doesn't have to.
How it works
- 1
Identify the vehicle
Send a 17-character VIN or an Israeli registration number. Both go in the same field, so your search box doesn't need to ask which one the customer typed.
- 2
Decode the configuration
AutoWiz resolves the identifier to brand, model, model code, year, engine model, engine capacity and fuel type, plus registration data such as road-entry date, test validity and tire sizes.
- 3
Match OEM part numbers
The decoded configuration is mapped to the OEM part numbers that fit that exact vehicle, each returned with a part name.
- 4
Filter to your stock
shop-parts intersects those OEM numbers with your synced product catalog and returns only what you carry, with your SKU, description, category and price.
A request and its response
Every call is a JSON POST with a bearer token. A plate number is enough to get the full decode:
curl -X POST https://api.autowiz.app/api/v2/get-car-info \
-H "Authorization: Bearer $AUTOWIZ_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "car_number_or_vin": "5777638" }'{
"vin": "JM1GJ1V58G1436763",
"vehicleNumber": "5777638",
"brand": "Mazda",
"year": 2016,
"modelName": "CX-5",
"modelCode": "CX5",
"engineModel": "PE",
"engineCapacity": 1998,
"fuelType": "בנזין",
"frontTire": "225/55R19",
"rearTire": "225/55R19",
"validUntilTestDate": "2025-12-31",
"roadEntryDate": "2016-01-01"
}The same identifier sent to get-car-parts returns the OEM numbers that fit:
POST /api/v2/get-car-parts
{ "car_number_or_vin": "5777638" }
[
{ "number": "PE0113440", "name": "Air Filter" },
{ "number": "PE0114302", "name": "Oil Filter" }
]Endpoints
| Endpoint | Input | Returns |
|---|---|---|
get-car-info | VIN or plate, or up to 20 in one batch | Decoded vehicle: brand, model, year, engine, fuel, tires, registration dates |
get-car-parts | VIN or plate | OEM part numbers and names that fit the vehicle |
shop-parts | VIN or plate | Only the matched parts in your catalog, with SKU, description, category, price and image |
get-3-parts-by-paramsV4 | Brand, year, model, engine capacity | The same parts list when the customer has no VIN or plate at hand |
Generic VIN decoder vs. AutoWiz
| Generic VIN decoder | AutoWiz VIN Decoder API | |
|---|---|---|
| Input | VIN only | VIN or Israeli plate number |
| Output | Vehicle specification | Vehicle specification plus fitting OEM parts |
| Inventory awareness | None | Filtered to the parts in your own catalog |
| Batch lookups | Varies | Up to 20 vehicles per request, per-item errors |
| Fallback search | None | Brand → year → model → engine drill-down endpoints |
Built for real workflows
Parts retailers and e-commerce
Put a plate or VIN box above your catalog and show only the parts that fit, without the customer knowing their engine code.
Workshops and service counters
Identify the car from its plate at check-in and have the right filter and brake part numbers ready before the car is on the lift.
Insurers and fleets
Validate vehicle details and registration dates for many vehicles at once with batch lookups of up to 20 per request.
7-day integration
A documented REST API with a small surface, so most teams go from first call to production in about a week.
Frequently asked questions
What can I send the VIN Decoder API?+
Either a 17-character VIN or an Israeli vehicle registration number (7–8 digits), in the same car_number_or_vin field. AutoWiz detects which one you sent and resolves both to the same vehicle record.
Does it just decode the VIN, or does it find parts too?+
Both. get-car-info returns the decoded vehicle, get-car-parts returns the OEM part numbers that fit it, and shop-parts narrows those down to the parts that exist in your own catalog, with your SKU, description and price.
Can I use plate numbers instead of a VIN?+
Yes, for vehicles registered in Israel. Counter staff can type the plate straight off the car, which is usually faster and less error-prone than reading a 17-character VIN from the windshield.
Can I look up more than one vehicle per request?+
Yes. get-car-info accepts up to 20 plates or VINs in a single batch request. Each result carries the identifier you sent, and a vehicle that can't be found returns its own error without failing the rest of the batch.
How is this different from a generic VIN decoder?+
A generic VIN decoder gives you make, model, and trim. AutoWiz connects that decode directly to your parts catalog, so the output is a list of parts you can sell, not just vehicle metadata.
How do I authenticate?+
Every request carries a bearer token in the Authorization header. You generate and revoke API keys yourself from your AutoWiz account once API access is enabled.
What happens if no parts match?+
get-car-parts and shop-parts return a 404 when the vehicle can't be found or has no mapped parts, so your UI can fall back to a brand, year, model and engine search instead of showing an empty list.
Related guides
Try VIN-to-part matching
See it against your own inventory, or talk to our team about integration.