Skip to main content

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.

This section covers Didit’s no-code engine integrations — pre-built apps for automation platforms that let you trigger verifications and listen to results without writing backend code. If you already write code against the Sessions API or use one of the SDKs, you do not need an engine — engines are designed for teams that want to wire Didit into operations tools (CRM, forms, spreadsheets, Slack) through drag-and-drop automation.

​
Supported engines

Zapier

Connect Didit to 6,000+ apps through Zapier. Create verification sessions, listen for status changes, and retrieve results — all through Zaps. Available today.

More engines

Make.com, n8n, Workato, and Power Automate are on the roadmap. Need one urgently? Ping us on WhatsApp and we will prioritise it.
Zapier is the only fully maintained engine integration today. Until more engines ship, the recommended path for non-Zapier automation platforms is to use Webhooks plus a generic “HTTP” or “Webhook” step in your tool of choice.

​
When to choose an engine integration

You want to…Best fit
Trigger a KYC session from a Google Form, Typeform, or HubSpot contactZapier
Push verification results into a spreadsheet, CRM, or Slack channelZapier
Email a custom message when a session is Approved or DeclinedZapier
Embed verification inside your own product UIWeb SDKs
Call the API directly from a backend serviceSessions API
Get raw webhook events into a no-code tool that has no Didit appWebhooks + the tool’s generic HTTP trigger

​
How engine integrations work

All engine apps wrap the same public REST API under the hood — there is no separate engine-only feature surface:
  1. The engine authenticates with your Didit API Key (Console → API & Webhooks).
  2. The engine’s action steps call POST /v3/session/ or GET /v3/session/{sessionId}/decision/ on your behalf.
  3. The engine’s trigger steps subscribe to your Didit webhooks — when a session status changes, the engine receives the event and starts your downstream Zap / scenario.
Because engines share the same surface as direct integrations, anything you can do in a Zap, you can also do by calling the API yourself — and the pricing, rate limits, and webhook signature rules are identical.

​
Pricing

Engine integrations are free to use — there is no Didit surcharge for routing through Zapier or any future engine. You only pay the standard pay-per-call price for whatever features the underlying session uses (ID verification, AML, liveness, etc.). Your automation tool’s own subscription costs (e.g. Zapier tasks) are separate and billed by them.

​
Next steps

Zapier setup guide

End-to-end walkthrough: connect your account, build your first Zap, react to results.

Webhooks reference

The event payloads and signature scheme every engine subscribes to under the hood.