# Choose your flow. See how to integrate it.

> Choose KYC, NFC, liveness, address and interview options. Generate your integration guide with the right API sequence and code examples.

Canonical URL: https://legichain.com/en/integration-guide
Language: en
Other language (tr): https://legichain.com/integration-guide
Other language (de): https://legichain.com/de/integration-guide
Other language (es): https://legichain.com/es/integration-guide
Other language (it): https://legichain.com/it/integration-guide

Choose your checks, arrange the steps you can move and select your technology. See which request goes where, and which token to use, step by step.

- [Build my guide](https://legichain.com/en/integration-guide#builder)
- [API reference](https://legichain.com/en/developers#api-reference)

## Shape your integration.

Your choices update the guide. They do not change account policy or create a real session.

Your choices update the guide. They do not change account policy or create a real session.

Drag or use the arrows. NFC stays after document reading. After KYC approval, you can reorder AML observation and address steps; interviews follow all selected checks. This order belongs to the API integration; interview question order comes from the panel flow.

This interview uses an existing persona_id and an approved retained KYC record for that persona. It does not recollect document sides, selfie, NFC or liveness. Choose “New KYC” if a new identity verification is needed.

The active published flow in your customer panel defines questions, their order, expected answer types and voices. This page does not change them; it explains how your app runs that flow through the API. Each session pins its flow version.

Keep the account API key on your backend. Never embed it in mobile or browser code; give the device only a session-scoped token.

Obtain compute_url and compute_token only from the API claim response. Upload raw bytes to that origin, not through the main API or as multipart.

For AI interviews, send only new fragments from one camera recording, not the entire video for every question. Use answer ranges, capture-state and finish conditions to progress.

When company auto-fallback is enabled, an eligible unverified AI result enters the manual queue after evidence is archived. A ready operator takes the call; otherwise the applicant waits. The app follows the returned manual state and connects to LiveKit only when media is present. No human reviewer approval is needed; explicit refusal or failed KYC cannot be bypassed. First poll GET /v3/onboardings/{id} with session_token. Read /manual only when the session is open, state=manual_waiting and interview_mode=manual; before the regional transition job completes, /manual may still return 404.

Combine the HTTP helpers with the step examples, fill placeholders from each API response and implement camera/NFC adapters. This is not a compiled SDK or a one-click app; the page sends no API requests.

[Build my guide](https://legichain.com/en/integration-guide#builder)

## Two connections, clear responsibilities.

- **Your backend → regional API** — Map personas, create sessions and follow results here. Keep your account API key on your backend. Use the TR or EU regional endpoint assigned to your account.
- **Your app → assigned compute** — Send documents, selfies and AI answer recordings directly to compute_url. The short-lived compute_token is scoped to that session. The platform selects dedicated or shared capacity and assigns the host.
- **Manual interview → LiveKit** — Follow the manual request and queue. Connect to LiveKit with returned participant details only when /manual contains media, meaning the call is active and recording is ready. Operator assignment alone is insufficient.

---
Legichain — technology for digital identity, AI Video KYC and risk screening. Contact: contact@legichain.com
