FAQ
What is the difference between the v1 and v2 API?
The v1 API is our legacy API. It's being maintained, but is not getting new features. You can read more about the differences between the the v1 API here, and the v2 API here.
How long will you support the v1 API?
We will support the v1 API until the end of 2025.
How can I reduce the latency?
BlinkID Verify is one of the fastest document verification solutions on the market. However, there are a few things you can do to reduce latency if you need it even lower or if your end users have challenging network conditions. By far the biggest impact comes from uploading and downloading images.
If you're using the Verify SDK, we already do all the possible optimizations on the images in the request.
If you're using BlinkID for capturing images, make sure not to mutate the images after capturing because it will cause issues and lead to poor UX (and migrate to the Verify SDK as soon as possible).
Here's a list of things you can do to reduce latency:
- Use the Verify SDK.
- Use the multipart endpoint.
- Disable image return for images you don't need (
returnFullDocumentImageand otherreturn*options). - If not using our SDKs, compress and resize the images before uploading (while following our image requirements)
- Disable checks you don't care about (e.g. if you accept photocopies, disable the
photocopyCheck)
Can I modify the images after capturing (and before sending them to the API)?
If you're using BlinkID or the Verify SDK for capturing images, no, you should not do this. It will cause issues and lead to poor UX.
If you're not using BlinkID or the Verify SDK, you can modify the images after capturing, but be mindful of our image requirements.
What does the fieldFormatCheck do?
The fieldFormatCheck validates whether certain fields follow the required format patterns. For example, if a date of birth is formatted as "07///07/2008", we can determine that the value is invalid or not genuine.
What does the suspiciousDataCheck do?
The suspiciousDataCheck is a check that looks for data in the document that seems suspicious, which can range from extremely suspicious to unlikely. The sampleStringCheck identifies strings such as "Sample Specimen", which are strong indicators that the document is not genuine. The suspiciousNumberCheck flags numbers that contain unrealistic sequences - for example, a document number represented as "123456789" would cause this check to fail.
What does the dataIntegrityCheck do?
The dataIntegrityCheck is all about making sure the document contains all the information that is expected on that particular version of the document, in the places and rough formats in should be in. Fraudsters can make omissions or subtle layout changes this check catches, but it can also easily be triggered by poor image quality.
Can I use a third party solution to capture images?
Yes, but we recommend using our SDKs for the best experience. Besides the fact we're very proud of our SDKs, and that we've worked very hard to make them the best, fastest, and most secure, there's a simple purely logical reason for this recommendation.
The Verify SDK is able to guarantee that the captured images are verifiable, i.e. that they will satisfy all of the image quality and other requirements of BlinkID Verify. This will provide the best experience for your users, but also save your time and money by avoiding recapturing and re-verifying images.
Can I use no solution to capture images?
Yes, but we heavily discourage this. It's insecure, doesn't guarantee image quality, and can lead to unexpected behavior of some checks. So, if you must do this, you should set the CaptureCondition UseCase parameter to NoControl so we can tweak Verify behavior to accomodate the conditions as much as possible.