Collection
Integration & API
Connect Didit with no-code links, reusable links, mobile and web SDKs or the API, get results with webhooks, and debug an integration that is not behaving.
Ways to integrate
5 articles- Ways to integrate: API, SDKs, and no-code linksYou don't need to write code to start verifying people with Didit - use a no-code link, or bring in an SDK or the API when you want automation.
- Mobile and web SDKsNative SDKs for iOS, Android, React Native and Flutter put the flow inside your app and are the only route that supports NFC. Web SDKs embed it on your site.
- Reusable verification linksOne long-lived link per workflow that starts a fresh session on every visit, ideal for a website button, a QR code or affiliates. Tag it with vendor_data.
- The Marketplace and bringing your own providerEvery Didit check is built in. The Marketplace lets you route a workflow step through your own account with a partner provider, with Didit as the fallback.
- How do I connect an AI agent (Claude, ChatGPT, Cursor) to Didit?Connect Claude, ChatGPT, Cursor or any MCP client from Developers, MCP and agents. The agent signs in with Didit, no API key, and you can revoke it at any time.
Getting results back
2 articles- Getting verification results with webhooksDidit does not email you when a verification changes status. Set up a webhook so your backend hears about it at once, and verify the signature first.
- Where do I find my API key, workflow ID and webhook secret?Your API key is under Developers, API keys; the workflow ID is on the Workflows page; the webhook signing secret is per endpoint under Developers, Webhooks.
Debugging
2 articles- When a webhook never arrivesCheck in order: the delivery log, the event name, the firewall, the signature. The Deliveries list shows whether Didit sent it, halving the problem at once.
- API errors and what they meanWhat each Didit API HTTP status means: 401 and 403 for keys and permissions, 402-style balance problems, 429 rate limits, and how to read the error body.