VINfix API 2.0 VINfix API Live 2.0 Demo

Overview

In North America and around the world, VIN is widely used as a primary information key in government vehicle registers, police information systems, auto insurance companies, auto leasing companies, auto repair shops, roadside assistance companies, etc. VIN data quality is essential not only for government administrative and security reasons but also very important in commercial applications. Most VIN errors occur in manual processes during transcribing or copying VINs from documents to information systems.

Our VINfix API 2.0 provides a powerful and reliable technology designed to help your clients correct typographical errors in problem VINs. Behind the scene, two state-of-the-art machine learning algorithms do the wonders. Utilizing unsupervised learning, they are trained on our huge in-house VIN database to find clusters of hidden grouping/patterns. These clusters are modeled by measuring similarity which is defined by various distance metrics.

Equipped with our VINfix technology, your clients will never have to scratch their heads when a VIN is tagged as "invalid" by VIN decoders and they most likely have no idea what's wrong with the VIN, let alone how to correct it. Our VINfix technology can figure that out for them in a split second.

What VINfix does

VINfix API 2.0 can help your clients correct any typographical errors in the 1st to 11th digits of a VIN, including the 9th digit, the so-called "checksum digit".

The most common typographical errors have been observed over the years when it comes to VIN entry:

Letter "S" vs Number "5" Letter "S" vs Number "2" Letter "H" vs Number "8"
Letter "G" vs Number "6" Letter "Z" vs Number "2" Letter "B" vs Number "8"
Letter "D" vs Number "0" Letter "U" vs Number "4" Letter "Y" vs Number "4"
Letter "C" vs Letter "L" Letter "M" vs Letter "N" Letter "U" vs Letter "V"
Letter "F" vs Letter "S" Letter "T" vs Letter "P" Letter "P" vs Letter "B"
Letter "E" vs Letter "B" Letter "E" vs Letter "F" Letter "E" vs Number "8"

These errors can be very difficult to spot once they have been introduced into VINs.

What VINfix doesn't do?

At least in the United States and Canada, the 12th to 17th digits in a VIN are the vehicle's serial or production sequence number. This is unique to each vehicle and every manufacturer uses their own sequences as there is no standard for this number. Our VINfix API makes no attempt to provide any suggestions on the "Serial Number" portion of a VIN.

VINfix service should never be used to alter VINs. It may be a crime to alter a VIN.

VINfix API 2.0 XML Examples

Problem VIN Corrected VIN VINfix Result
1HTM6ZPM6LH00XXXX 1HTMGZPM6LH00XXXX https://www.vinquery.com/samples/ws_vinfix_1.xml
JH2KF01038K20XXXX JH2KF0103HK20XXXX https://www.vinquery.com/samples/ws_vinfix_5.xml
19XFBSF53CE31XXXX 19XFB2F53CE31XXXX https://www.vinquery.com/samples/ws_vinfix_6.xml
1SGGD22121102XXXX 15GGD22121102XXXX https://www.vinquery.com/samples/ws_vinfix_7.xml
19VAA65536A0XXXX 19UUA65536A0XXXX https://www.vinquery.com/samples/ws_vinfix_8.xml
1ACLN385XDK19XXXX 1ACCN385XDK19XXXX https://www.vinquery.com/samples/ws_vinfix_9.xml

VINfix API 2.0 Json Examples

Problem VIN Corrected VIN VINfix Result
1HTM6ZPM6LH00XXXX 1HTMGZPM6LH00XXXX https://www.vinquery.com/samples/ws_vinfix_1.json
JH2KF01038K20XXXX JH2KF0103HK20XXXX https://www.vinquery.com/samples/ws_vinfix_5.json
19XFBSF53CE31XXXX 19XFB2F53CE31XXXX https://www.vinquery.com/samples/ws_vinfix_6.json
1SGGD22121102XXXX 15GGD22121102XXXX https://www.vinquery.com/samples/ws_vinfix_7.json
19VAA65536A0XXXX 19UUA65536A0XXXX https://www.vinquery.com/samples/ws_vinfix_8.json
1ACLN385XDK19XXXX 1ACCN385XDK19XXXX https://www.vinquery.com/samples/ws_vinfix_9.json