API integration
VIN Decoding Guides
A practical starting guide for using the VehiCode VIN decoder API in automotive products.
Start with a normalized VIN
VIN decoding quality starts with normalization. Remove spaces, convert letters to uppercase, and validate the VIN length before sending it to the API.
VehiCode returns a compact public vehicle report designed for product and backend integrations.
Decode request
curl -X POST https://vehicode.eu/api/decode \
-H "Content-Type: application/json" \
-H "x-api-key: vdx_your_api_key" \
-d '{"vin":"WVWZZZAUZHP507470"}'Store useful vehicle fields
Most integrations should persist the original VIN, manufacturer, model, body style, model year, vehicle type, and any technical specifications returned by the API.
Avoid storing internal diagnostics. Public API responses intentionally exclude internal notes, source details, and confidence labels.
Plan for corrections
Vehicle data can be incomplete or inconsistent across regions and data sources. Use the correction endpoint when your system knows the expected result.
Correction reports help improve reviewed rules and future decode quality.
FAQ
Should I call the VIN decoder from the browser?
No. Subscriber API keys should be used from trusted backend systems so the full key stays private.
Can I report an incorrect decode?
Yes. Subscriber integrations can report expected manufacturer, model, body style, model year, and a short note.