> ## 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 Didit et intégrations : Web, mobile & Zapier

> Intégrez la KYC Didit dans vos apps web, mobiles et backend : SDK web et natifs, SDK serveur Python, Node.js, Go, Java, PHP, Ruby et .NET, et plugins.

> [!NOTE]
>
> Pour la connexion des utilisateurs finaux, voir [Authentification](https://docs.didit.me/fr/authentication/overview.md). Pour combiner vérification, surveillance et connexion, utilisez le [prompt d'intégration partagé](https://docs.didit.me/fr/integration/integration-prompt.md). La disponibilité du SDK d'Authentification est indépendante des versions du SDK de vérification ci-dessous.

AI Agent Integration Prompt
        Copier le prompt dans le presse-papiers



      
      

\<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>



      
      

Coller dans

Choisissez la manière d'intégrer Didit en fonction de votre plateforme et de votre cas d'usage.> [!NOTE]
>
> ### Recommandé : intégration SDK via les sessions
>
> Pour la vérification destinée aux utilisateurs (onboarding KYC, vérification de l'âge, contrôles d'identité), nous recommandons **l'intégration SDK via des sessions hébergées**. Les parcours de vérification font l'objet de tests A/B et sont optimisés pour les taux de complétion les plus élevés, la plus grande rapidité et le meilleur niveau de sécurité. Tous les SDK (web, iOS, Android, React Native et Flutter) sont **disponibles dès maintenant**.
>
> Depuis votre backend, utilisez un [SDK serveur](https://docs.didit.me/fr/integration/server-sdks/overview.md) pour Python, Node.js, Go, Java, PHP, Ruby ou .NET afin de créer ces sessions, lire les décisions et vérifier les webhooks. Pour les opérations de serveur à serveur (traitement par lots, pipelines personnalisés), appelez les **API autonomes** avec ces mêmes SDK. Consultez la [documentation de l'API autonome](https://docs.didit.me/fr/standalone-apis/id-verification.md) pour les endpoints de vérification individuels.> [!WARNING]
>
> Si vous lancez une session Didit depuis votre propre produit, vous restez responsable de la couche d'information et de consentement côté responsable du traitement. Avant que l'utilisateur ne commence la vérification, indiquez que Didit fournit le workflow, liez votre propre avis de confidentialité et recueillez un consentement explicite lorsque celui-ci est requis pour la capture du document, du selfie, de la détection du vivant ou des données biométriques. Voir [Sécurité et conformité](https://docs.didit.me/fr/getting-started/security-compliance.md), [Marque blanche](https://docs.didit.me/fr/console/white-label.md) et [Créer une session](https://docs.didit.me/fr/sessions-api/create-session.md).Cette leçon de Didit Academy vous permet de réaliser une intégration complète en une seule fois : le SDK, les clés API pour chaque environnement, l'appel de création de session et un gestionnaire de webhook qui vérifie le secret de signature.[Le guide complet d'intégration — Didit Academy](https://www.youtube.com/embed/fX03-WEu_EI?rel=0\&playsinline=1)***## WebIntégrez la vérification à votre application web avec JavaScript, une iframe ou une redirection.> [card] [SDK web](https://docs.didit.me/fr/integration/web-sdks/overview.md)
>
> SDK JavaScript, intégration par iframe ou redirection. React, Vue, Angular, JavaScript natif.> [card] [SDK JavaScript](https://docs.didit.me/fr/integration/web-sdks/javascript-sdk.md)
>
> Contrôle programmatique complet avec callbacks d'événements et TypeScript.> [card] [Iframe InContext](https://docs.didit.me/fr/integration/web-sdks/incontext-iframe.md)
>
> Intégrez la vérification dans votre page. Aucun backend requis avec UniLink.> [card] [Redirection](https://docs.didit.me/fr/integration/web-sdks/web-redirect.md)
>
> Redirigez vers le parcours hébergé par Didit. Prise en charge multi-appareils.***## MobileDes SDK natifs pour une expérience optimale de la caméra, du NFC et de la détection du vivant sur l'appareil.> [card] [SDK natifs](https://docs.didit.me/fr/integration/native-sdks/overview.md)
>
> iOS, Android, React Native, Flutter. Prise en charge complète du NFC et de la biométrie.> [card] [SDK iOS](https://docs.didit.me/fr/integration/native-sdks/ios-sdk.md)
>
> SwiftUI et UIKit. Lecture du passeport NFC. Disponible dès maintenant.> [card] [SDK Android](https://docs.didit.me/fr/integration/native-sdks/android-sdk.md)
>
> Kotlin et Jetpack Compose. Prise en charge du NFC. Disponible dès maintenant.> [card] [React Native](https://docs.didit.me/fr/integration/native-sdks/react-native-sdk.md)
>
> API TypeScript multiplateforme encapsulant les SDK natifs iOS et Android. Prise en charge du NFC. Disponible dès maintenant.> [card] [Flutter](https://docs.didit.me/fr/integration/native-sdks/flutter-sdk.md)
>
> API Dart multiplateforme encapsulant les SDK natifs iOS et Android. Prise en charge du NFC. Disponible dès maintenant.> [card] [Repli WebView](https://docs.didit.me/fr/integration/web-sdks/webview-in-ios-android.md)
>
> Solution de repli pour les plateformes sans SDK natif. Privilégiez les SDK natifs lorsqu'ils sont disponibles.***## ServeurBibliothèques officielles pour votre backend : appels typés vers les API serveur de Didit, vérification des webhooks et contrôles des tokens d'Authentification.> [card] [SDK serveur](https://docs.didit.me/fr/integration/server-sdks/overview.md)
>
> Matrice d'installation, configuration, erreurs et gestion des versions.> [card] [Python](https://docs.didit.me/fr/integration/server-sdks/python.md)
>
> Clients synchrones et asynchrones. Python 3.10+.> [card] [Node.js](https://docs.didit.me/fr/integration/server-sdks/node.md)
>
> Types TypeScript, ESM et CommonJS. Node.js 18+.> [card] [Go](https://docs.didit.me/fr/integration/server-sdks/go.md)
>
> Bibliothèque standard uniquement. Go 1.22+.> [card] [Java](https://docs.didit.me/fr/integration/server-sdks/java.md)
>
> Java et Kotlin, synchrones et asynchrones. Java 11+.> [card] [PHP](https://docs.didit.me/fr/integration/server-sdks/php.md)
>
> Tout client HTTP PSR-18. PHP 8.1+.> [card] [Ruby](https://docs.didit.me/fr/integration/server-sdks/ruby.md)
>
> Compatible Rails, construit sur net/http. Ruby 3.1+.> [card] [.NET](https://docs.didit.me/fr/integration/server-sdks/dotnet.md)
>
> C#, asynchrone, injection de dépendances. .NET 8 et .NET Standard 2.0.***## IntégrationsPlugins et outils sans code pour les plateformes populaires.> [card] [Zapier](https://docs.didit.me/fr/integration/engines/zapier.md)
>
> Automatisez la vérification grâce à des déclencheurs et actions sans code.> [card] [WordPress et WooCommerce](https://docs.didit.me/fr/integration/web-sdks/wordpress-woocommerce.md)
>
> Plugin pour les sites WordPress et WooCommerce.> [card] [Shopify](https://docs.didit.me/fr/integration/web-sdks/shopify.md)
>
> Vérifiez les acheteurs et restreignez l'accès aux produits soumis à une limite d'âge sur Shopify.> [card] [Salesforce](https://docs.didit.me/fr/integration/web-sdks/salesforce.md)
>
> Déclenchez des vérifications Didit depuis les flux et les enregistrements Salesforce.***## Comparaison rapide| Plateforme | Méthode | Statut | NFC | Caméra | Idéal pour |
| - | - | - | :-: | - | - |
| Web | JavaScript SDK | ✅ Disponible | — | Navigateur | Contrôle total, React / Vue / Angular |
| Web | InContext Iframe | ✅ Disponible | — | Navigateur | Intégration rapide, sans backend requis |
| Web | Redirect | ✅ Disponible | — | Navigateur | Multi-appareils, configuration simple |
| iOS | Native SDK | ✅ Disponible | ✅ | Optimisée | Meilleure UX, lecture de la puce NFC |
| Android | Native SDK | ✅ Disponible | ✅ | Optimisée | Meilleure UX, lecture de la puce NFC |
| React Native | Native SDK | ✅ Disponible | ✅ | Optimisée | Meilleure UX, lecture de la puce NFC |
| Flutter | Native SDK | ✅ Disponible | ✅ | Optimisée | Meilleure UX, lecture de la puce NFC |
| Backend | Server SDKs (Python, Node.js, Go, Java, PHP, Ruby, .NET) | ✅ Disponible | — | — | Sessions, décisions, API autonomes, webhooks |
| No-Code | Zapier | ✅ Disponible | — | — | Workflows automatisés |
| CMS | WordPress | ✅ Disponible | — | — | Sites WP / WooCommerce |
| Commerce | Shopify | ✅ Disponible | — | — | Boutiques Shopify |
| CRM | Salesforce | ✅ Disponible | — | — | Flux et enregistrements Salesforce |## Prochaines étapes> [card] [Flux complet via l’API](https://docs.didit.me/fr/integration/api-full-flow.md)
>
> Intégration de sessions de bout en bout : création de sessions, webhooks, résultats.> [card] [Webhooks](https://docs.didit.me/fr/integration/webhooks.md)
>
> Recevez les mises à jour du statut de vérification en temps réel.***


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