FAQ
Please review this page carefully before contacting our support team.
Please note: If you haven't found a solution and need technical support, describe the issue as detailed as possible, including the steps you took to solve or reproduce it. Also please provide the log file, which can be found in the Web API installation directory. This will help us to find and fix the issue. Thank you!
Please use the Regula Download Manager tool.
Check that WebApiSdkService is up and running
Check the base address in the WebApiServiceHost.exe.config file located in the Web API installation directory; by default it is
<add key="ServiceAddress" value="http://localhost"/>Make sure that there are no other programs or services listening to the same port
Make sure that you submit requests with the correct URL
If you are trying to access a built-in client or online documentation, please check that appropriate features are enabled in the WebApiServiceHost.exe.config file and restart the service
<add key="UseOnlineDocumentation" value="true"/><add key="UseBuiltinClient" value="true"/>
Make sure that there are no other programs or services already occupying the configured port. Try to change the port in the WebApiServiceHost.exe.config file and start the service again.
The username / password combination for accessing the server is TestUser / Regul@SdkTest.
Authentication is not required on client installations, as in most cases it makes the integration into existing systems harder. You can ignore the authentication request and perform other requests without specifying X-Token
It can be done in the WebApiServiceHost.exe.config file located in the Web API installation directory:<add key="ServiceAddress" value="http://localhost"/>
change the service base address appropriately
<add key="ServiceAddress" value="https://localhost:443"/>Make sure, that no process or application is using the selected port
Assign a valid certificate to the port using command
netsh http add sslcert ipport=0.0.0.0:443certhash={your certificate Thubmprint}appid={your application ID}
4. Restart the service to apply the changes
It means that Regula SDK is not initialized correctly. It usually happens because the license is invalid. Please run the Regula Licensing application and send us a screenshot of its main window.
Check that you have the latest versions of SDK and document database installed
Check that you have the correct type of document database installed (WorldDocs or AllDocs)
Make sure that you have specified the Document Type recognition in the Capabilities, when submitting the transaction
Make sure that the document image meets our quality requirements​
Please send the incorrectly recognized document sample to our support team
[{ "Base64ImageString": "base64 string","Format": ".jpg","LightIndex": 6,"PageIndex": 0},{ "Base64ImageString": "base64 string","Format": ".jpg","LightIndex": 6,"PageIndex": 1}]
You should submit both document pages within a single transaction as in the example below. Please mark every separate page image with a different page index value. The transaction will be processed as usual. When the results are ready, the XML or JSON structure will contain a list with the results in accordance to the requested result type (for each page).
The error occurs when your request (body + headers) exceeds the maximum allowed request length. By default, the limit value is set to 5MB. You can change this setting in the WebApiServiceHost.exe.config file:
<add key="MaxRequestSizeKB" value="5120"/>
Log file(s) is located in the Web API installation directory. By default it is C:\Program Files (x86)\Regula\Document Reader Web API\API
Yes. You can enable / disable it by setting the following property value:
<add key="UseBuiltinClient" value="true"/>
Check if the READERDEMO.exe process is fully initialized (consuming ~400mb of memory)
Make sure that you have specified the appropriate capabilities value to receive this kind of result when submitting the transaction
Make sure that image meets our quality requirements​
Check if the document you submitted actually contains the requested result type
The error occurs when the SDK exceeds the allowed time limit for a single transaction. To prevent transaction queue jamming, the transaction will be dropped and marked with an error status. The queue will proceed.
To extend the maximum transaction processing time, change the following property in the WebApiServiceHost.exe.config file:
<add key="SdkMaxProcessingTime" value="10"/>
The default capabilities value used on the demo website api.regulaforensics.com is 500. It includes MRZ, Visual Zone OCR, Document Type, Visual Graphics and Barcode Processing.
A transaction is discarded from the Web API service memory in 1 minute after processing is finished. After this period you will not be able to retrieve the results.
Minimal requirements:
CPU - Intel i5 2.0+ GHz
RAM - 8+ Gb
HDD free space - 10 Gb
OS - Windows Windows Server 2008 R2+
A single request can use more than one core which, in its turn, can increase the speed of image processing. However, it will not change the fact that the SDK will perform processing of transactions in queue mode, not concurrently.
If you need to increase the processing speed, you can run multiple VMs. You are free to use as many servers (VMs) as needed to guarantee the proper performance of the system. But in this case, every single server (VM) would require a new license key.
