Trusted by more than 1000 brands worldwide
Also looking for a solid partner? Give us a ring at +31 50 2111631
Uploading documents to the API
The first step is providing a picture or a PDF file of a document containing a VIN to our API. Usually this is done from a mobile app, email, FTP or web application.
Image to text using OCR
As soon as a picture or PDF has been received, it is converted to a TXT file. In this step all the text from the document is extracted, but it is not yet structured.
Getting JSON output from the API
The Klippa Parser takes the TXT gained from the OCR in step 2 and converts it into structured JSON using machine learning. The JSON is then returned as output from the API. The VIN on the document is now extracted. From here the field can easily be processed into your database.
The image on the left is a simplified example of the JSON response. More fields can be extracted if required.
Spend less on extracting VINs by using Klippa.
Process VINs automatically within seconds. Perfect for the automotive industry.
Prevent manual data entry errors with high quality data extraction of VINs.
Automatically recognize errors, duplicates and fraud.
Which documents can you scan for VINs?
Below is a list of documents for which you can use VIN scanning. This is not an exhaustive list, but depends on what the client requires.
Frequently Asked Questions
What does VIN OCR cost?What VIN standards are supported?What kind of clients are using Klippa?What languages does Klippa support?Is Klippa VIN processing GDPR-compliant?Can Klippa convert documents to CSV, XLSX, XML or JSON?
What does VIN OCR cost?
The pricing structure for Klippa VIN capturing depends on the amount of documents. Both pay per use and monthly licenses are available. Get in contact with our product specialists to get an exact quote.
What VIN standards are supported?
There are at least four competing standards used to calculate the VIN. In general, we support all standards, including:
– FMVSS 115, Part 565, as used in the United States and Canada
– ISO 3779, as used in Europe and many other parts of the world
– SAE J853, very similar to the ISO standard
– ADR 61/2, as used in Australia, referring to ISO 3779 and 3780
In case you wonder if we support a certain VIN or have any other question, feel free to contact us.
What kind of clients are using Klippa?
Klippa’s engine extracts as much data as possible from documents via OCR and machine learning. We support many different types of clients, because our engine is so versatile. VIN scanning is mostly used by clients in the automotive, insurance and rental sector.
What languages does Klippa support?
All European languages are supported. Our engine performs best on documents in English, Dutch, Norwegian, Danish, Swedish, Finnish, Italian, Portuguese, Spanish, German, Hebrew and French. Other languages can be supported on request, we’d just need to train our machine learning models.
Is Klippa VIN capturing GDPR-compliant?
All the services that Klippa offers are fully GDPR-compliant. By default, we use ISO-certified servers within the European Union for processing. If you are not located within the EU, we can also set up servers in a region of choice.
Next to that, a data processor agreement is in place. We do not store any of your or your customers’ data after processing.
Can Klippa convert VINs to CSV, XLSX, XML or JSON?
Yes we can. Klippa takes pictures of documents, or their PDF equivalents, and converts them to readable text using OCR. From there we use machine learning to turn the text into structured data. Most of the time we use JSON for this, but depending on your preferences we can also convert documents to CSV, XLSX or XML.
Schedule a free online demonstration
Get a clear view of how Klippa can help make your VIN processing more efficient. A demo takes just 30 minutes.
Please feel free to ask all your questions.
Get in touch by email, phone or chat!
+31 50 2111631