> For the complete documentation index, see [llms.txt](https://finext.gitbook.io/one-kyc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://finext.gitbook.io/one-kyc/api/flows.md).

# Flows

A verification scenario (flow) defines the set, order, and parameters of the steps that a user goes through during KYC. Flows are created and edited in the **admin panel** (visual flow editor, templates, version management).

## Using flows in the Tenant API

When you create a verification link, include **`flow_id`** in the request body:

<mark style="color:green;">`POST`</mark> `undefined/v1/kyc/verification-links`

You can obtain available flow identifiers in two ways:

* In the admin panel, **Flows** section.
* Through the Admin API (if you need automation).

Flow execution happens on the OneKYC side. Once the link is created, the user opens it and goes through every flow step on the OneKYC verification page.

## Flow structure

Every flow includes the following components:

* **Verification steps** — the set of stages a user completes. Document liveness and face liveness are bundled inside the document and selfie steps respectively.
* **Transition rules** — define the order in which steps run.
* **Parameters** — document requirements, check settings, webhook configuration.
* **Branding** — visual styling: colour palette, logo, UI copy.

***

For detailed verification-link handling, see [Verification links](/one-kyc/api/verification-links.md).