---
title: "Intro to the SDK | Veriff.com"
slug: "quick-guide-of-idv-using-the-sdks-1"
description: "Quick and lightweight introduction to Veriff's Software Development Kits for end-user verification."
updated: 2025-06-06T13:56:26Z
published: 2025-06-06T13:56:26Z
canonical: "devdocs.veriff.com/quick-guide-of-idv-using-the-sdks-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://devdocs.veriff.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Intro to the SDK

> [!TIP]
> See platform-specific SDK documentation in the [SDK Guides](/v1/docs/sdk-guide) section

Opt for the **Software Development Kits (SDKs)** when you **prefer using Veriff's front-end solution and built-in** verification flow, and have no plans to independently collect end-user media.

This **article aims to give a quick intro** into using Veriff services via **Software Development Kits (SDKs).**

---

## Quick overview of the steps

1. Pick and add the relevant Veriff SDK to your project (see the relevant [SDK guide](/v1/docs/sdk-guide) for more info)
2. [Create an integration](/v1/docs/how-to-create-an-integration)
3. [Set up webhooks](https://devdocs.veriff.com/v1/docs/webhooks-guide#set-up-webhooks)
4. [Create a verification session](/v1/docs/how-to-generate-sessions-manually) to get the session URL
  1. Using the [POST /sessions](https://devdocs.veriff.com/apidocs/v1sessions) API call
  2. Using the [JavaScript SDK](/v1/docs/javascript-sdk-1)
5. Pass the session URL to the SDK
6. Direct the end-user to the verification flow, where they submit their data and media
7. End-user's data and media is passed to Veriff
8. Veriff verifies the end-user
9. Veriff returns the decision [via the decision webhook](/v1/docs/decision-webhook)

---

## SDK session lifecycle diagram

![SDK flow diagram: customer creates a session, gets a session URL, and directs the end-user to it. End-user verifies; Veriff sends a decision](https://cdn.document360.io/5c26138b-b1e9-404e-a2e4-c83a49245be7/Images/Documentation/SDK_flow_diagram.jpg?sv=2026-02-06&spr=https&st=2026-10-26T07%3A48%3A43Z&se=2026-10-26T08%3A48%3A43Z&sr=c&sp=r&sig=s07QKa4H80NZEmbRQdzCEpx08nNhj6lxKPHdVTXA4pQ%3D)

*The diagram above illustrates a verification process flow between three entities: end-user, customer, and Veriff.*

| Step | End-User | Customer | Veriff |
| --- | --- | --- | --- |
| 1 |  | Creates session by sending POST request to "/sessions" | Returns session URL in `verification.url` parameter |
| 2a | **Native SDK users:** Starts verification session using Veriff mobile SDK with provided verification URL |  |  |
| 2b | **Web SDK users:** Is directed to the verification URL to begin verification |  |  |
| 3 | Completes verification flow on device |  |  |
| 4a | **Native SDK users:** Taken back to customer's application |  |  |
| 4b | **Web SDK users:** Redirected to destination set by customer (e.g., `verification.callback`) |  |  |
| 5 |  | Receives decision | Sends decision to customer via webhook |

The diagram uses dashed vertical lines to represent the timeline for each entity and horizontal arrows to show the direction of communication between them. A horizontal green bar represents the end-user completing the verification flow, and another green bar indicates "Session is verified" at the conclusion.

---

## Changelog

| Date | Description |
| --- | --- |
| Jun 6, 2025 | Header “Article versioning” renamed to “Changelog” |
| Mar 31, 2025 | SDK session lifecycle diagram updated Diagram description added |
| Mar 12, 2025 | Documentation published |

A **process where the end-user submits the data** required to get verified.

Also referred to as the "end-user flow".

**User of Veriff customer's solution**, the person who goes through the verification flow (aka "end-user flow").

This where the end-user is directed to go through the verification flow, and it is **unique for each verification session**.

It is a combination of the `base URL` and the `sessionToken`, created as soon as a verification session is created. You can find its value in the response payload of your POST /sessions call, as `verification.url`.

## Related

- [SDK Guides](/sdk-guide.md)
- [Integrations](/how-to-create-an-integration.md)