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

# SDK e integrazioni Didit: web, mobile e Zapier

> Integra la verifica KYC di Didit in app web, mobile e backend: SDK web e nativi, SDK server per Python, Node.js, Go, Java, PHP, Ruby e .NET, plugin.

> [!NOTE]
>
> Per l'autenticazione degli utenti finali, vedi [Autenticazione](https://docs.didit.me/it/authentication/overview.md). Per combinare verifica, monitoraggio e accesso, usa il [prompt di integrazione condiviso](https://docs.didit.me/it/integration/integration-prompt.md). La disponibilità dell'SDK di autenticazione è separata dalle versioni degli SDK di verifica indicate di seguito.

AI Agent Integration Prompt
        Copia il prompt negli appunti



      
      

\<pre>

\``I want to integrate Didit identity verification into my application. Analyze my project and recommend the best integration approach.

\## My Project Context
\[Describe your stack: framework, language, web vs mobile, etc.]

\## Two Integration Approaches

Didit offers two main integration approaches. Choose based on your use case:

\### Approach 1: SDK Integration via Sessions (RECOMMENDED)
Best for: User-facing verification flows (KYC onboarding, age verification, identity checks).
How it works: Your backend creates a session, your frontend presents a verification UI using an SDK, the user completes verification, and your backend receives results via webhook.
Why recommended: Didit-hosted verification flows are A/B tested and optimized for the highest completion rates, fastest speed, and best security. The SDKs handle camera permissions, NFC, liveness detection, document capture, and all edge cases out of the box.

\### Approach 2: Standalone API (Direct REST Calls)
Best for: Server-to-server operations, batch processing, custom verification pipelines, or when you want full control over the verification UI.
How it works: Your backend calls Didit APIs directly for individual checks (ID verification, AML screening, liveness, face matching, age estimation, phone/email verification, proof of address, etc.).
When to use: When you already have your own capture UI, when you're doing backend-only batch processing, or when you need to compose individual verification steps into a custom pipeline.
Docs: Each standalone API has its own documentation under [Standalone APIs](https://docs.didit.me/standalone-apis/id-verification.md).

\## SDK Availability — All SDKs Are Available

\### For Web Apps
1\. **JavaScript SDK** (@didit-protocol/sdk-web) — RECOMMENDED for web. Works with React, Vue, Angular, Next.js, Nuxt, Svelte, and vanilla JS. Modal and inline/embedded modes. Full TypeScript support. Install: npm install @didit-protocol/sdk-web
2\. InContext Iframe — Embed verification in your page with <iframe>. Simplest setup, no npm needed. Good for quick prototypes.
3\. Redirect — Redirect user to Didit-hosted page, they return via callback URL. Best for cross-device flows or when iframe camera access is problematic.
4\. WordPress/WooCommerce Plugin — For WordPress sites. No-code setup.
5\. Shopify Plugin — For Shopify stores. No-code setup.
6\. Salesforce — Salesforce-side integration. See /integration/web-sdks/salesforce.

\### For Mobile Apps (ALWAYS prefer native SDKs over WebView)
1\. **iOS Native SDK** — RECOMMENDED for iOS. Swift/SwiftUI/UIKit. iOS 13.0+ (NFC requires iOS 15.0+). Best UX, NFC passport/ID reading, optimized camera, 54 languages. SPM: https://github.com/didit-protocol/sdk-ios. CocoaPods: pod 'DiditSDK'
2\. **Android Native SDK** — RECOMMENDED for Android. Kotlin/Jetpack Compose. minSdk 23 (Android 6.0+); ML auto-detection on API 24+. Best UX, NFC, optimized camera, 54 languages. Maven: me.didit:didit-sdk (via https://raw.githubusercontent.com/didit-protocol/sdk-android/main/repository)
3\. **React Native SDK** — RECOMMENDED for React Native. RN 0.76+ (New Architecture), iOS 13.0+ / Android API 24+. Cross-platform TypeScript API wrapping native iOS and Android SDKs. NFC support, Expo config plugin (development build required). Install: npm install @didit-protocol/sdk-react-native
4\. **Flutter SDK** — RECOMMENDED for Flutter. Flutter 3.3+, Dart 3.11+, iOS 13.0+ / Android API 23+. Cross-platform Dart API wrapping native iOS and Android SDKs. NFC support. pub.dev: didit_sdk
5\. WebView (FALLBACK ONLY) — Only use if no native SDK is available for your platform. Loses NFC, camera optimization, and biometric integration.

\### For Backend/Server
1\. **Server SDKs** — RECOMMENDED for backend code. Official typed libraries for the Didit server APIs, with webhook signature verification built in. Python: pip install didit-sdk. Node.js/TypeScript: npm install @didit-protocol/sdk-node. Go: go get github.com/didit-protocol/sdk-go. Java/Kotlin: me.didit:didit-java. PHP: composer require didit-protocol/sdk-php guzzlehttp/guzzle. Ruby: gem install didit-sdk. .NET: dotnet add package Didit. Each reads DIDIT_API_KEY. Docs: https://docs.didit.me/integration/server-sdks/overview
2\. REST API — Server-to-server, for languages without a server SDK. Create sessions, retrieve results, manage users, call standalone APIs.
3\. Webhooks — Receive real-time verification results asynchronously.
4\. Zapier — No-code automation for verification workflows.

\## SDK Session Integration Architecture (Recommended Flow)

\### Step 1: Backend creates a session
With a server SDK: client.sessions.create(workflow_id=..., vendor_data=..., callback=...) (same method in every language, in its own case). The raw request:
POST https://verification.didit.me/v3/session/
Headers: { "x-api-key": DIDIT_API_KEY, "Content-Type": "application/json" }
Body: {
"workflow_id": DIDIT_WORKFLOW_ID,
"callback": "https://myapp.com/done",
"vendor_data": "internal-user-id"
}
Response: {
"session_id": "uuid",
"session_token": "jwt",
"verification_url": "https://verify.didit.me/...",
"status": "Not Started"
}

\### Step 2: Present verification to user (choose one)
\- Web JS SDK: DiditSdk.shared.startVerification({ url: verification_url })
\- Iframe: embed verification_url in <iframe>
\- Redirect: window.location.href = verification_url
\- iOS/Android/RN/Flutter native SDK: DiditSdk.startVerification(token: session_token)

\### Step 3: Receive results via webhook
Your backend receives POST with:
\{
"session_id": "uuid",
"status": "Approved" | "Declined" | "In Review" | "In Progress" | "Abandoned",
"vendor_data": "internal-user-id",
"decision": { ... }
}
With a server SDK, webhooks.verify(raw_body, headers, WEBHOOK_SECRET) does all of the checks below and returns a typed event. Without one, verify the webhook signature (HMAC-SHA256, lowercase hex). Pick one header:
\- X-Signature-V2 = HMAC(WEBHOOK_SECRET, canonical_json) — recommended; canonical_json is the body re-serialized with sorted keys, compact separators, and unescaped Unicode (survives middleware re-encoding).
\- X-Signature = HMAC(WEBHOOK_SECRET, raw_body) — simplest, but only if you read the exact raw bytes before any parser touches them.
Also reject if abs(now - X-Timestamp) > 300 and use a constant-time compare. Full scheme: /integration/webhooks

\### Step 4: Update your database
\- "Approved" → user.verified = true, store decision data
\- "Declined" → user.verification_status = "declined", log warnings
\- "In Review" → user.verification_status = "pending_review"
\- "Abandoned" → send reminder to user
\- "Expired" → create new session

\## Decision Data Model (from webhook or GET /v3/session/{id}/decision/)
Every per-feature result is a PLURAL ARRAY (one entry per workflow node). Never code against a singular key like `nfc` or `id_verification`.
\{
"session_id": "uuid",
"session_kind": "KYC",
"status": "Approved",
"id_verifications":    [{ "node_id": "feature_ocr", "status": "Approved", "first_name": "John", "last_name": "Doe", "document_type": "Passport" }],
"nfc_verifications":   [{ "node_id": "feature_nfc", "status": "Approved" }],
"liveness_checks":     [{ "node_id": "feature_liveness", "status": "Approved", "score": 0.99, "method": "passive" }],
"face_matches":        [{ "node_id": "feature_face_match", "status": "Approved", "score": 95 }],
"aml_screenings":      [{ "node_id": "feature_aml", "status": "Approved", "total_hits": 0, "hits": [] }],
"phone_verifications": [{ "node_id": "feature_phone", "status": "Approved", "full_number": "+14155552671", "is_disposable": false }],
"email_verifications": [{ "node_id": "feature_email", "status": "Approved", "email": "alex.sample@example.com", "is_breached": false }],
"ip_analyses":         [{ "node_id": "feature_ip",    "status": "Approved" }]
}

\## Choosing the Right Approach

\| Question | → Use SDK Sessions | → Use Standalone API |
\|----------|-------------------|---------------------|
\| User-facing verification? | ✅ Yes | For custom capture UI only |
\| Need highest completion rate? | ✅ Yes (A/B tested flows) | You manage UX yourself |
\| Need NFC passport reading? | ✅ Yes (native SDKs) | Not available |
\| Batch/backend processing? | Not ideal | ✅ Yes |
\| Custom verification pipeline? | Limited to workflows | ✅ Full flexibility |
\| Fastest integration? | ✅ Minutes with UniLink | Requires more setup |

\## Rate Limits
\- POST /v3/session/: 600 session creations per minute per application (scope: session-v2-create). Applies to every application — there is no separate free-tier limit on V3 today.
\- GET endpoints: 300 requests per minute per application (generic-get).
\- Write endpoints (POST/PATCH/DELETE): 300 per minute per application (generic-write).
\- Transaction creates and event ingestion (POST /v3/transactions/, POST /v3/events/, POST /v3/events/batch/): 600 per minute per application (ingest-write), instead of the generic write budget.
\- 429 responses include X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset (epoch seconds), and Retry-After. See /integration/rate-limiting.

\## Environment Variables Needed
\- DIDIT_API_KEY — from Didit Console > API & Webhooks
\- DIDIT_WEBHOOK_SECRET — from Didit Console > API & Webhooks
\- DIDIT_WORKFLOW_ID — from Didit Console > Workflows

\## AI Agent Skills (for Cursor, Claude Code, etc.)
Install pre-built skills: npx clawhub@latest install didit-sessions
GitHub: https://github.com/didit-protocol/skills

\## Docs
\- Quick Start: https://docs.didit.me/getting-started/quick-start
\- API Full Flow: https://docs.didit.me/integration/api-full-flow
\- Webhooks: https://docs.didit.me/integration/webhooks
\- Standalone APIs: https://docs.didit.me/standalone-apis/
\- API Reference: https://docs.didit.me/api-reference/overview

Based on my project, please:
1\. Recommend the best integration approach (SDK sessions vs standalone API) and the best method for my platform
2\. Create the backend endpoint to create sessions (or standalone API calls)
3\. Create the frontend component/view to present verification (if SDK approach)
4\. Create the webhook endpoint to receive results
5\. Add database schema updates to track verification status``

\</pre>



      
      

Incolla in

Scegli come integrare Didit in base alla tua piattaforma e al tuo caso d'uso.> [!NOTE]
>
> ### Consigliato: integrazione SDK tramite sessioni
>
> Per la verifica rivolta agli utenti (onboarding KYC, verifica dell'età, controlli dell'identità), ti consigliamo l'**integrazione SDK tramite sessioni ospitate**. I flussi di verifica sono sottoposti a test A/B e ottimizzati per i tassi di completamento più alti, la massima velocità e la migliore sicurezza. Tutti gli SDK (web, iOS, Android, React Native e Flutter) sono **disponibili ora**.
>
> Dal tuo backend, usa uno [SDK lato server](https://docs.didit.me/it/integration/server-sdks/overview.md) per Python, Node.js, Go, Java, PHP, Ruby o .NET per creare quelle sessioni, leggere le decisioni e verificare i webhook. Per le operazioni server-to-server (elaborazioni batch, pipeline personalizzate), chiama le **API standalone** tramite gli stessi SDK. Consulta la [documentazione delle API standalone](https://docs.didit.me/it/standalone-apis/id-verification.md) per gli endpoint di verifica individuali.> [!WARNING]
>
> Se avvii una sessione Didit dal tuo prodotto, sei comunque responsabile del livello di informativa e consenso lato titolare del trattamento. Prima che l'utente inizi la verifica, informalo che il flusso è gestito da Didit, collega la tua informativa sulla privacy e raccogli il consenso esplicito dove richiesto per l'acquisizione di documenti, selfie, rilevamento della vitalità o dati biometrici. Vedi [Sicurezza e compliance](https://docs.didit.me/it/getting-started/security-compliance.md), [White Label](https://docs.didit.me/it/console/white-label.md) e [Crea sessione](https://docs.didit.me/it/sessions-api/create-session.md).Questa lezione di Didit Academy configura un'integrazione completa in un'unica sessione: l'SDK, le chiavi API per ambiente, la chiamata per creare la sessione e un gestore di webhook che verifica il segreto di firma.[La guida completa all'integrazione — Didit Academy](https://www.youtube.com/embed/fX03-WEu_EI?rel=0\&playsinline=1)***## WebIntegra la verifica nella tua app web con JavaScript, iframe o reindirizzamento.> [card] [SDK web](https://docs.didit.me/it/integration/web-sdks/overview.md)
>
> SDK JavaScript, incorporamento tramite iframe o reindirizzamento. React, Vue, Angular, JavaScript vanilla.> [card] [SDK JavaScript](https://docs.didit.me/it/integration/web-sdks/javascript-sdk.md)
>
> Controllo programmatico completo con callback di eventi e TypeScript.> [card] [InContext Iframe](https://docs.didit.me/it/integration/web-sdks/incontext-iframe.md)
>
> Incorpora la verifica nella tua pagina. Nessun backend richiesto con UniLink.> [card] [Reindirizzamento](https://docs.didit.me/it/integration/web-sdks/web-redirect.md)
>
> Reindirizza al flusso ospitato da Didit. Supporto su più dispositivi.***## MobileSDK nativi per la migliore esperienza su dispositivo con fotocamera, NFC e rilevamento della vitalità.> [card] [SDK nativi](https://docs.didit.me/it/integration/native-sdks/overview.md)
>
> iOS, Android, React Native, Flutter. Supporto completo per NFC e biometria.> [card] [SDK iOS](https://docs.didit.me/it/integration/native-sdks/ios-sdk.md)
>
> SwiftUI e UIKit. Lettura del passaporto via NFC. Disponibile ora.> [card] [SDK Android](https://docs.didit.me/it/integration/native-sdks/android-sdk.md)
>
> Kotlin e Jetpack Compose. Supporto NFC. Disponibile ora.> [card] [React Native](https://docs.didit.me/it/integration/native-sdks/react-native-sdk.md)
>
> API TypeScript multipiattaforma che incapsula gli SDK nativi iOS e Android. Supporto NFC. Disponibile ora.> [card] [Flutter](https://docs.didit.me/it/integration/native-sdks/flutter-sdk.md)
>
> API Dart multipiattaforma che incapsula gli SDK nativi iOS e Android. Supporto NFC. Disponibile ora.> [card] [Fallback WebView](https://docs.didit.me/it/integration/web-sdks/webview-in-ios-android.md)
>
> Alternativa per le piattaforme senza SDK nativo. Preferisci gli SDK nativi quando disponibili.***## ServerLibrerie ufficiali per il tuo backend: chiamate tipizzate alle API server di Didit, verifica dei webhook e controlli dei token di autenticazione.> [card] [SDK server](https://docs.didit.me/it/integration/server-sdks/overview.md)
>
> Matrice di installazione, configurazione, errori e versionamento.> [card] [Python](https://docs.didit.me/it/integration/server-sdks/python.md)
>
> Client sincroni e asincroni. Python 3.10+.> [card] [Node.js](https://docs.didit.me/it/integration/server-sdks/node.md)
>
> Tipi TypeScript, ESM e CommonJS. Node.js 18+.> [card] [Go](https://docs.didit.me/it/integration/server-sdks/go.md)
>
> Solo libreria standard. Go 1.22+.> [card] [Java](https://docs.didit.me/it/integration/server-sdks/java.md)
>
> Client sincroni e asincroni per Java e Kotlin. Java 11+.> [card] [PHP](https://docs.didit.me/it/integration/server-sdks/php.md)
>
> Qualsiasi client HTTP PSR-18. PHP 8.1+.> [card] [Ruby](https://docs.didit.me/it/integration/server-sdks/ruby.md)
>
> Compatibile con Rails, basato su net/http. Ruby 3.1+.> [card] [.NET](https://docs.didit.me/it/integration/server-sdks/dotnet.md)
>
> C#, supporto asincrono e iniezione delle dipendenze. .NET 8 e .NET Standard 2.0.***## IntegrazioniPlugin e strumenti senza codice per le piattaforme più diffuse.> [card] [Zapier](https://docs.didit.me/it/integration/engines/zapier.md)
>
> Automatizza la verifica con trigger e azioni senza codice.> [card] [WordPress & WooCommerce](https://docs.didit.me/it/integration/web-sdks/wordpress-woocommerce.md)
>
> Plugin per siti WordPress e WooCommerce.> [card] [Shopify](https://docs.didit.me/it/integration/web-sdks/shopify.md)
>
> Verifica gli acquirenti e limita l'accesso ai prodotti con restrizioni di età su Shopify.> [card] [Salesforce](https://docs.didit.me/it/integration/web-sdks/salesforce.md)
>
> Avvia verifiche Didit da flussi e record di Salesforce.***## Confronto rapido| Piattaforma | Metodo | Stato | NFC | Fotocamera | Ideale per |
| - | - | - | :-: | - | - |
| Web | JavaScript SDK | ✅ Disponibile | — | Browser | Controllo completo, React / Vue / Angular |
| Web | InContext Iframe | ✅ Disponibile | — | Browser | Integrazione rapida, senza backend |
| Web | Redirect | ✅ Disponibile | — | Browser | Multi-dispositivo, configurazione semplice |
| iOS | SDK nativo | ✅ Disponibile | ✅ | Ottimizzata | Migliore UX, lettura del chip NFC |
| Android | SDK nativo | ✅ Disponibile | ✅ | Ottimizzata | Migliore UX, lettura del chip NFC |
| React Native | SDK nativo | ✅ Disponibile | ✅ | Ottimizzata | Migliore UX, lettura del chip NFC |
| Flutter | SDK nativo | ✅ Disponibile | ✅ | Ottimizzata | Migliore UX, lettura del chip NFC |
| Backend | SDK server (Python, Node.js, Go, Java, PHP, Ruby, .NET) | ✅ Disponibile | — | — | Sessioni, decisioni, API autonome, webhook |
| No-Code | Zapier | ✅ Disponibile | — | — | Workflow automatizzati |
| CMS | WordPress | ✅ Disponibile | — | — | Siti WP / WooCommerce |
| Commerce | Shopify | ✅ Disponibile | — | — | Negozi Shopify |
| CRM | Salesforce | ✅ Disponibile | — | — | Flussi e record di Salesforce |## Prossimi passi> [card] [Flusso completo API](https://docs.didit.me/it/integration/api-full-flow.md)
>
> Integrazione end-to-end delle sessioni: creazione di sessioni, webhook, risultati.> [card] [Webhook](https://docs.didit.me/it/integration/webhooks.md)
>
> Ricevi aggiornamenti in tempo reale sullo stato della verifica.***


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.