Developer-first JSON
Responses are designed for backend integrations: predictable JSON, stable field names, and usage metadata with each subscriber request.
VIN Decoder API
VehiCode helps developers decode VINs into structured vehicle data for automotive platforms, internal tools, marketplaces, and subscriber API integrations.
VIN segments, vehicle identity fields, optional specs, and monthly usage metadata.
Free returns basic fields; paid plans unlock premium specs where available.
Vehicle Identification API
The VehiCode VIN Decoder API is a developer-facing endpoint for turning a VIN into a compact public vehicle report. It normalizes vehicle identification data, returns usage metadata, and keeps internal diagnostics out of client responses.
Responses are designed for backend integrations: predictable JSON, stable field names, and usage metadata with each subscriber request.
The public API returns useful vehicle fields and removes internal notes, source details, confidence labels, and operational diagnostics.
Subscriber systems can report incorrect decodes for review, which creates a practical feedback loop for improving vehicle data quality over time.
European VIN decoding
European vehicle data is messy in a very practical way. The same model can appear under different names across markets, body styles are not always encoded consistently, and public VIN sources often stop before they become useful for real product workflows.
VehiCode is built for that reality: decode what can be trusted, return clean client-safe data, and let correction reports improve the reviewed rule base over time.
Vehicle data API
The API always returns the VIN and structural fields it can derive from the submitted value. Free access returns core identity and basic specs. Starter and Business API keys add available premium technical specifications, dimensions, weight, and factory details. Clients receive compact JSON without empty internal explanation fields.
vinwmivdsvischeckDigityearCodeplantCodeserialNumbervalidFormatmanufacturermodelmodelCodegenerationbodyStylepossibleBodyStylestrimvehicleTyperegionmodelYearenginefuelTypetransmissiondriveTypepowerKwpowerHpdisplacementCcbatteryCapacityKwhemissionsStandardmarketlengthMmwidthMmheightMmwheelbaseMmcurbWeightKggrossWeightKggroundClearanceMmcargoVolumeLiterscargoVolumeMaxLitersDecode VIN API
Use x-api-key for subscriber usage. Authorization: Bearer is also supported.
POSTcurl -X POST https://vehicode.eu/api/decode \
-H "Content-Type: application/json" \
-H "x-api-key: vdx_your_api_key" \
-d '{"vin":"WVWZZZAUZHP507470"}'{
"report": {
"vin": "WVWZZZAUZHP507470",
"wmi": "WVW",
"vds": "ZZZAUZ",
"validFormat": true,
"manufacturer": "Volkswagen",
"model": "Golf",
"bodyStyle": "Combi",
"modelYear": "2017",
"region": "Europe"
},
"metadata": {
"plan": "business",
"upgradeAvailable": false,
"premiumFieldsAvailable": 0
},
"usage": {
"limit": 2500,
"remaining": 2499,
"resetAt": "2026-08-01T00:00:00.000Z"
}
}VIN Lookup API
Pre-fill listing fields and normalize vehicle labels from VIN input.
Decode VINs during acquisition, appraisal, import, and stock intake.
Keep vehicle records consistent across countries, vendors, and internal tools.
Attach cleaner vehicle identity data to intake, handover, and correction processes.
Pricing
A VIN Decoder API accepts a vehicle identification number and returns structured vehicle data that software can store, validate, or use to pre-fill workflows.
No. Public API responses are compact and omit internal notes, source details, confidence labels, and AI diagnostics.
Yes. VehiCode is built with European vehicle data workflows in mind, where VIN coverage often depends on manufacturer patterns, regional data quality, and reviewed rules.
The Free plan includes 25 requests / month. Starter includes 500 requests / month. Business includes 2,500 requests / month. Limit and reset metadata is returned with API responses.
Yes. Subscriber integrations can send correction reports with the expected manufacturer, model, body style, model year, and a note for admin review.
Start building
Create an account, generate an API key, and test the decode endpoint from your backend workflow.