> ## 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.

# SDKs & Integrationen: Web, Mobile & Zapier

> Didit KYC in Web-, Mobile- und Backend-Apps integrieren: native SDKs, Server-SDKs für Python, Node.js, Go, Java, PHP, Ruby, .NET sowie Plugins.

> [!NOTE]
>
> Informationen zur Endbenutzer-Anmeldung finden Sie unter [Authentication](https://docs.didit.me/de/authentication/overview.md). Um Verifizierung, Überwachung und Anmeldung zu kombinieren, nutzen Sie den [gemeinsamen Integrations-Prompt](https://docs.didit.me/de/integration/integration-prompt.md). Die Verfügbarkeit der Authentifizierungs-SDKs ist unabhängig von den unten aufgeführten Versionen der Verifizierungs-SDKs.

AI Agent Integration Prompt
        Prompt in die Zwischenablage kopieren



      
      

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



      
      

Einfügen in

Wählen Sie die für Ihre Plattform und Ihren Anwendungsfall passende Integrationsmethode für Didit.> [!NOTE]
>
> ### Empfohlen: SDK-Integration über Sitzungen
>
> Für benutzerseitige Verifizierungen (KYC-Onboarding, Altersverifikation, Identitätsprüfungen) empfehlen wir die **SDK-Integration über gehostete Sitzungen**. Die Verifizierungsabläufe sind A/B-getestet und auf höchste Abschlussraten, maximale Geschwindigkeit und beste Sicherheit optimiert. Alle SDKs – Web, iOS, Android, React Native und Flutter – sind **ab sofort verfügbar**.
>
> Verwenden Sie in Ihrem Backend ein [Server-SDK](https://docs.didit.me/de/integration/server-sdks/overview.md) für Python, Node.js, Go, Java, PHP, Ruby oder .NET, um diese Sitzungen zu erstellen, Entscheidungen abzurufen und Webhooks zu verifizieren. Für Server-to-Server-Operationen (Batch-Verarbeitung, benutzerdefinierte Pipelines) rufen Sie die **Standalone-APIs** über dieselben SDKs auf. Die einzelnen Verifizierungs-Endpoints finden Sie in der [Dokumentation der Standalone-APIs](https://docs.didit.me/de/standalone-apis/id-verification.md).> [!WARNING]
>
> Wenn Sie eine Didit-Sitzung aus Ihrem eigenen Produkt heraus starten, sind Sie weiterhin für die Hinweis- und Einwilligungsebene auf Seiten des Verantwortlichen zuständig. Bevor der Benutzer die Verifizierung startet, müssen Sie offenlegen, dass Didit den Workflow bereitstellt, Ihre eigene Datenschutzerklärung verlinken und eine ausdrückliche Einwilligung einholen, sofern dies für die Erfassung von Dokumenten, Selfies, Liveness-Daten oder biometrischen Daten erforderlich ist. Siehe [Sicherheit & Compliance](https://docs.didit.me/de/getting-started/security-compliance.md), [White-Label](https://docs.didit.me/de/console/white-label.md) und [Sitzung erstellen](https://docs.didit.me/de/sessions-api/create-session.md).Diese Lektion der Didit Academy zeigt eine vollständige Integration in einem Durchgang: das SDK, API-Schlüssel pro Umgebung, der Aufruf zum Erstellen einer Sitzung und ein Webhook-Handler, der das Signaturgeheimnis verifiziert.[Der vollständige Integrationsleitfaden — Didit Academy](https://www.youtube.com/embed/fX03-WEu_EI?rel=0\&playsinline=1)***## WebIntegrieren Sie die Verifizierung per JavaScript, Iframe oder Weiterleitung in Ihre Webanwendung.> [card] [Web-SDKs](https://docs.didit.me/de/integration/web-sdks/overview.md)
>
> JavaScript-SDK, Iframe-Einbindung oder Weiterleitung. React, Vue, Angular, Vanilla JS.> [card] [JavaScript-SDK](https://docs.didit.me/de/integration/web-sdks/javascript-sdk.md)
>
> Vollständige programmatische Kontrolle mit Event-Callbacks und TypeScript.> [card] [InContext-Iframe](https://docs.didit.me/de/integration/web-sdks/incontext-iframe.md)
>
> Betten Sie die Verifizierung in Ihre Seite ein. Mit UniLink ist kein Backend erforderlich.> [card] [Weiterleitung](https://docs.didit.me/de/integration/web-sdks/web-redirect.md)
>
> Weiterleitung zum von Didit gehosteten Ablauf. Geräteübergreifende Unterstützung.***## MobileNative SDKs für das beste Kamera-, NFC- und Liveness-Erlebnis direkt auf dem Gerät.> [card] [Native SDKs](https://docs.didit.me/de/integration/native-sdks/overview.md)
>
> iOS, Android, React Native, Flutter. Vollständige NFC- und Biometrie-Unterstützung.> [card] [iOS-SDK](https://docs.didit.me/de/integration/native-sdks/ios-sdk.md)
>
> SwiftUI und UIKit. Auslesen von NFC-Reisepässen. Ab sofort verfügbar.> [card] [Android-SDK](https://docs.didit.me/de/integration/native-sdks/android-sdk.md)
>
> Kotlin und Jetpack Compose. NFC-Unterstützung. Ab sofort verfügbar.> [card] [React Native](https://docs.didit.me/de/integration/native-sdks/react-native-sdk.md)
>
> Plattformübergreifende TypeScript-API, die native iOS- und Android-SDKs kapselt. NFC-Unterstützung. Ab sofort verfügbar.> [card] [Flutter](https://docs.didit.me/de/integration/native-sdks/flutter-sdk.md)
>
> Plattformübergreifende Dart-API, die native iOS- und Android-SDKs kapselt. NFC-Unterstützung. Ab sofort verfügbar.> [card] [WebView-Fallback](https://docs.didit.me/de/integration/web-sdks/webview-in-ios-android.md)
>
> Fallback für Plattformen ohne natives SDK. Bevorzugen Sie native SDKs, sofern verfügbar.***## ServerOffizielle Bibliotheken für Ihr Backend: typisierte Aufrufe der Didit-Server-APIs, Webhook-Verifizierung und Prüfung von Authentifizierungs-Tokens.> [card] [Server-SDKs](https://docs.didit.me/de/integration/server-sdks/overview.md)
>
> Installationsmatrix, Konfiguration, Fehler und Versionierung.> [card] [Python](https://docs.didit.me/de/integration/server-sdks/python.md)
>
> Synchrone und asynchrone Clients. Python 3.10+.> [card] [Node.js](https://docs.didit.me/de/integration/server-sdks/node.md)
>
> TypeScript-Typen, ESM und CommonJS. Node.js 18+.> [card] [Go](https://docs.didit.me/de/integration/server-sdks/go.md)
>
> Nur Standardbibliothek. Go 1.22+.> [card] [Java](https://docs.didit.me/de/integration/server-sdks/java.md)
>
> Java und Kotlin, synchron und asynchron. Java 11+.> [card] [PHP](https://docs.didit.me/de/integration/server-sdks/php.md)
>
> Jeder PSR-18-HTTP-Client. PHP 8.1+.> [card] [Ruby](https://docs.didit.me/de/integration/server-sdks/ruby.md)
>
> Rails-kompatibel, basiert auf net/http. Ruby 3.1+.> [card] [.NET](https://docs.didit.me/de/integration/server-sdks/dotnet.md)
>
> C#, asynchron, Dependency Injection. .NET 8 und .NET Standard 2.0.***## IntegrationenPlugins und No-Code-Tools für gängige Plattformen.> [card] [Zapier](https://docs.didit.me/de/integration/engines/zapier.md)
>
> Automatisieren Sie Verifizierungen mit No-Code-Auslösern und -Aktionen.> [card] [WordPress & WooCommerce](https://docs.didit.me/de/integration/web-sdks/wordpress-woocommerce.md)
>
> Plugin für WordPress- und WooCommerce-Websites.> [card] [Shopify](https://docs.didit.me/de/integration/web-sdks/shopify.md)
>
> Verifizieren Sie Käufer und beschränken Sie den Zugang zu altersbeschränkten Produkten auf Shopify.> [card] [Salesforce](https://docs.didit.me/de/integration/web-sdks/salesforce.md)
>
> Lösen Sie Didit-Verifizierungen über Salesforce-Flows und -Datensätze aus.***## Schneller Vergleich| Plattform | Methode | Status | NFC | Kamera | Ideal für |
| - | - | - | :-: | - | - |
| Web | JavaScript-SDK | ✅ Verfügbar | — | Browser | Vollständige Kontrolle, React / Vue / Angular |
| Web | InContext-Iframe | ✅ Verfügbar | — | Browser | Schnelle Einbindung, kein Backend erforderlich |
| Web | Weiterleitung | ✅ Verfügbar | — | Browser | Geräteübergreifend, einfache Einrichtung |
| iOS | Natives SDK | ✅ Verfügbar | ✅ | Optimiert | Beste UX, Auslesen von NFC-Chips |
| Android | Natives SDK | ✅ Verfügbar | ✅ | Optimiert | Beste UX, Auslesen von NFC-Chips |
| React Native | Natives SDK | ✅ Verfügbar | ✅ | Optimiert | Beste UX, Auslesen von NFC-Chips |
| Flutter | Natives SDK | ✅ Verfügbar | ✅ | Optimiert | Beste UX, Auslesen von NFC-Chips |
| Backend | Server-SDKs (Python, Node.js, Go, Java, PHP, Ruby, .NET) | ✅ Verfügbar | — | — | Sitzungen, Entscheidungen, eigenständige APIs, Webhooks |
| No-Code | Zapier | ✅ Verfügbar | — | — | Automatisierte Workflows |
| CMS | WordPress | ✅ Verfügbar | — | — | WP- / WooCommerce-Websites |
| Handel | Shopify | ✅ Verfügbar | — | — | Shopify-Shops |
| CRM | Salesforce | ✅ Verfügbar | — | — | Salesforce-Flows und -Datensätze |## Nächste Schritte> [card] [Vollständiger API-Ablauf](https://docs.didit.me/de/integration/api-full-flow.md)
>
> Durchgängige Sitzungsintegration: Sitzungen erstellen, Webhooks, Ergebnisse.> [card] [Webhooks](https://docs.didit.me/de/integration/webhooks.md)
>
> Erhalten Sie Statusaktualisierungen zur Verifizierung in Echtzeit.***


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