English
Dutch
Go to website
Back
Articles on:
Technical OCR/APi
Questions answered about the technical side
Where are the Klippa servers located?
By default, Klippa’s servers are hosted by Microsoft Azure and they are located in Amsterdam, Netherlands. Other hosting options are possible, namely: deployment in region of choice, dedicated hosting, private/on-premise deployment.
Some readers
How long does it take to get the output from the API back?
In general the time between upload and JSON response varies between 1-15 seconds. Factors that influence the output time are document size, amounts of pages, and the amount of fields that are extracted.
Some readers
How does Klippa train the OCR parsing-engine?
We partially train the parser based on rules. That entails finding patterns by the eye and making sure that the system also recognizes the pattern. Partially it is based on Machine Learning: we tell the machine what value is correct, feeds it a big set of data and the ML-model will find the patterns among the data. We operate continuous improvement every two weeks.
Some readers
How does the OCR process multi-page PDF’s?
By default we look at the first and last page. There is a template that processes multi-page documents, activation upon use case.
Some readers
How does the OCR connect to our system?
Via the API. It is well documented in the following doccument: https://custom-ocr.klippa.com/docs
Some readers
How does the Klippa OCR-API work with our system?
The Klippa OCR and your software/system communicate with each other per means of an API. The API documentation provides the technical instructions on how the Klippa OCR connects to your software and which data points can be extracted. The API documentation can be found under: https://custom-ocr.klippa.com/docs
Some readers
What are the languages supported for the SDK?
All the platforms that supports native elements.
Some readers
What information, if any, is stored in logs/audit trails and do the API calls prevent caching of data?
The logs show timestamps of each API request we see, including a processing time and an API address. The API actively makes use of data caching to optimize the processing speed.
Some readers
Deprecating TLS 1.0 and TLS 1.1
On August 1st, 2021, Klippa will be deprecating support for Transport Layer Security (TLS) versions 1.0 and 1.1 to align with industry best practices for security and data integrity. What is TLS? Transport Layer Security (TLS) is a protocol that secures your data as it traverses the internet. Whenever you visit the Klippa website, use any of our apps (Linux, macOS, or Windows), or make requests using the Klippa API, TLS helps keep your data secure. Early versions of the TLS protocol are no
Few readers
List of Sub-processors Custom OCR API
To perform our services, we may make use of other software. Some will be data controllers by themselves, other will be deemed as (sub)processors according to our agreed Data Processor Agreement. This is a list of provider we work with, last updated on June 23rd 2021. Processors: Microsoft Azure: Microsoft Ireland Operations Ltd. Carmenhall Road Sandyford, Dublin 18, Ireland For data processing on their servers in the West Europe region. https://docs.microsoft.com/en-us/cloud-app-se
Some readers