Frequently Asked Questions

On this page, we collected all those questions that our customers usually ask – so you can have them answered before getting touch with us. Browse topics from technical details to pricing questions – and if you still have questions, feel free to reach out to us.

General questions

Our service is built upon REST API that is programming language independent, anything that can initiate a TCP / IP connection can be used.

Our service is platform independent: Windows, Linux, Android, iOS…

REST API can be easily called from a programming environment such as Java, JavaScript, PHP, C ++, C #, Python, Swift or even Curl, without deeper programming knowledge. It is also possible to use the JAVA SDK which makes integration even easier by using objects.

You need to know the business logic of your own solution and the programming language of your application. You must be able to use the REST API to invoke the service. Read more about how to start using the service.

ANPR Cloud



Start using the service

You will receive a code to confirm your registration by email and activate your account. Login to your ANPR Cloud DevPortal and walk through our how-to-use page. See the steps of registration →

We support countries all over the world with characters in many different languages. In our European DevPortal we support these countries.

On the node sides it is 80ms! Since we are talking about network communication, it can be up to 500ms depending on the current state of your network and size of image you sent (please keep it under 200kbyte).

What makes our service easy to use is that it does not require any classic integration skills whatsoever. That means no special expertise is needed: with intermediate, general IT skills, anybody can perform the setup. You only need to know how to use REST API and understand the JSON format.

The ANPR Cloud REST API can be accessed in any language. To learn about the REST API, more information can be found in our DevPortal’s how-to-use page and client side sample code on GitHub.

Data usage

No data is stored in ANPR Cloud. Your data are used only for the recognition process, temporarily stored in the Amazon web server’s ultra-encrypted storage before being entirely deleted. Both, images submitted to the cloud and the data sent back to your system, are secured with SSL encryption. All data are managed according to EU’s GDPR regulation. Please review our Data Processing Agreement and our Privacy Agreement.

ANPR Cloud does not use any of your content (such as images) for any purpose except to provide you with the ANPR Cloud API service.

We will not make the image that you send available to the public, or share it with anyone else, except as necessary to provide the ANPR Cloud API service. For example, we use third-party vendor (AWS services) to help us provide some aspect of our services, such as storage or transmission of data, who will be under appropriate security and confidentiality contractual obligations. We will not share the image that you send with any other parties, or make it public, for any other purpose. Please review our Data Processing Agreement.

When you send an image to ANPR Cloud API, we must store that image for a short period of time (80-200ms) in order to perform the recognition and return the results to you. For online (immediate response) operations, the image data is processed in memory and not persisted to disk.

We use HTTPS channel for communication and AWS security services.

ANPR Cloud does not claim any ownership of any of the content (including images) that you transmit to the ANPR Cloud API.


Yes, our free subscription (trial) does not require any payment information. Once you use up all 200 of your free credits, you have to wait until the beginning of the next month, when you will be granted another 200 transactions. This amount of credit is perfectly enough to make sure of the quality of our service and at the same time test whether the image produced by your camera is suitable for cloud processing.

Every account comes with 200 free credits. Beyond the free tier, ANPR Cloud credits must be purchased through AWS Marketplace or Stripe.

Except as otherwise noted, our prices are exclusive of applicable taxes and duties, including VAT and applicable sales tax.

We only charge for HTTP 200 and 400 status codes.

The HTTP 200 OK success status response code indicates that the request has succeeded. The response will contain a result in JSON format.

The HTTP 400 is an Invalid Image error message. This means that the size (the image is less than 10MB) and format (jpeg, bmp, etc.) of the image was correct, but the vehicle and license plate are not recognizable on it by the service. That is, the service was executed and the algorithm and resources processed the image but we could not provide a usable result.

To prevent this error happening, in the testing phase, please use our demo application on the Dashboard and use images generated by your camera.

One credit is always deducted per still image for processing.

For example, if you want us to return a max. five license plates per one image, set the optional parameter maxreads to five and if we find two, we subtract three credits. If, on the other hand, we find all five plates that you requested, we will only deduct five credits because we are no longer trying sixth time because of the value of maxreads.

By default, maxreads are always 1, recognition is 0 or 1.

Of course, ANPR Cloud will notify you when you have reached 80% of your pre-purchased credit package and so you have the opportunity to decide whether to purchase a larger package or not. We’ll also let you know when you’ve reached the maximum limit for your credit package. Of course, we do not stop the service, but continue to provide it at a flat rate.

Input image

The recognition algorithm behind the ANPR Cloud (a neural network) was taught to process images taken by various cameras containing 40+ million different license plates in all around the world. The boundaries of recognition capabilities are extremely wide, better than what the human eye can recognize. However, if the attributes of the image containing the vehicle and license plate provided by your camera are outside the training data set, the neural network may not be able to see the vehicle and license plate. To avoid this, the client side and the recognition service must be synchronized. How? Go to the demo interface of DevPortal Dashboard and upload some typical images. If the returned results are good then there is nothing to do, if not, then please see the camera settings and input image guide description of our how-to-use subpage.

The characteristics of the input image determine the quality of the ANPR and MMR service, i.e., speed, accuracy, low False Positive rate etc.

What is a good input image?

First, including the vehicle and the license plate, which is clearly visible, i.e. distortion-free, contrasting, legible characters, etc.

We write about it on the DevPortal’s how-to-use subpage, or if you want to read more about it, take a look at our input image guide.

Also, what is a good image? Small sized (around 100kbyte) i.e. compressed image format. Why? Because we are talking about a network service, i.e. small image = fast network communication and fast processing. In this way we can achieve 80ms processing time values. It is not always easy to take small-sized and good ANPR images if we have to solve the task with a surveillance camera or a mobile phone. In this case, the client-side image selection is an important task.

The best approach is to test your ’hard-to-read images’ using the DevPortal demo application.

Client-side integration

Calling the service is REST-based and we give a step by step guide on the DevPortal’s how-to-use page. REST-based http calls can be integrated into any programming language environment. We provide sample code in Curl, C++ SDK, JavaScript and Java SDK that will guide you building up the client-side implementation. The Curl and JavaScript code elements can be found on the DevPortal’s how-to-use page, while the Java SKD and C++ SDK implementation has been uploaded to GitHub.


Representational state transfer (REST) is a software architectural style that defines a set of constraints to be used for creating Web services. Learn more about in at Wikipedia.

To learn how to use it please visit stackoverflow, best practices

The service is based on the request to response structure, i.e. we call the service with http post, the input data is wrapped in JSON data format and ANPR Cloud sends a response. Upon successful processing (HTTP 200) the response is packaged in JSON data format, upon unsuccessful processing, it sends a HTTP error status that must be handled by the client-side implementation.

You can find the http status codes on the DevPortal how-to-use subpage by clicking on ANPR Cloud API field:

  • Input Image issues: HTTP 400, 413 error messages. In this case, please check the input image guide and correct the camera settings or the image preselection module in your application.


  • API key issues: HTTP 401, 403 In this case, check the DevPortal’s how-to-use subpage for a valid API key per user and update your application.
  • You have run out of free credit: HTTP 429. In this case, please subscribe for a monthly package (overview subpage on your Dashboard).


  • Network issues: HTTP 408, 500, 503, 504. Since we are talking about a network service, there may be server problems. In this case, no processing will take place and, of course, no credit will be deducted. On our side, we have minimized this risk by solving all infrastructure elements with AWS services and AWS availability is 99.9999%.These status messages must also be handled on the client side. We recommend that exception handling be considered. We advise this in the Java SDK (see exception handling section).

Still have questions?