Documentation menu
Integration options
There are three ways to put Blink KYC in front of a customer. All three use the same session and the same result, so you can start with one and add another later.
Blink SDK
Embed verification in your own app or website. The SDK talks to Blink with the session token your backend created, and you choose how much of the screen it owns:
| Mode | What you build | Best for |
|---|---|---|
| Drop-in | Nothing — Blink's capture screens handle guidance, auto-capture and liveness. | Most integrations. Fastest, best capture quality. |
| Your screens | Your own camera UI; the SDK tells you what to capture next and uploads it. | A fully bespoke design. |
| Headless | You supply the image bytes; the SDK only runs the protocol. | Custom camera stacks or kiosks. |
Hosted link
No SDK in your product at all: build a link from the session token and send the customer to Blink's hosted verification page — by button, SMS or QR code. See Hosted links.
Server API
Your backend always uses the Session API to start a verification and the Result API to read it, whichever front end you choose. The device-side calls are made for you by the SDK and the hosted page; they are documented under Device API for reference.
Comparison
| SDK | Hosted link | |
|---|---|---|
| Code in your app | A few lines | None |
| Stays inside your app | Yes | Opens Blink's page |
| Branding | Colours, copy, your own screens | Blink's page |
| Backend work | The same: create the session, read the result | |