---
Source: https://docs.microblink.com/verify/client-side-sdk/third-party
Title: Third party SDK
---

# Third party SDK

It's possible to use a third party SDK to capture images for the Verify API.
This is generally not recommended, because the Verify SDK will typically provide a better experience, but there are use cases where that's not possible.

## Configuration

It's important to configure the third party SDK as best as possible for use with the Verify SDK.

To start with, **make sure it's able to capture images according to the [image requirements](/verify/image-requirements)**.

Be prepared for the Verify SDK to return `Retry` or `Undeterminable` [`RecommendedOutcome`s](/verify/core-concepts/recommended-outcome) and develop a UI/UX for retries.

The Verify API processes **single images** for the front and the back of the document, so make sure to select only the best ones if your SDK captures multiple frames.

## Image processing

When using BlinkID, or the Verify SDK, the images **cannot** be modified in any way.
However, when you're using a third party SDK, **you're free of this constraint**.
Feel free to compress, resize, or otherwise modify the images if needed, but make sure to follow the [image requirements](/verify/image-requirements).

## Barcode frames

The Verify API can accept an optional third image that contains a **close up of the barcode**.
This is useful when the barcode is particularly dense and isn't readable with full context.
If your SDK has the capability to capture this frame, make sure to pass it to the API when needed.
For more details, take a look at the [request API reference](/verify/api/ref/v2#model/documentverificationrequest).


Last updated on Apr 16, 2026