didit-sessions

To create KYC verification sessions via API, post a workflow_id to the API and redirect the user to the returned verification URL. You can then manage sessions through a unified API surface covering decisions retrieval, status updates, and deletion.

A unified API surface for identity verification orchestrates multiple workflow sessions from a single endpoint, preventing errors and delays. It manages session creation, blocklist enforcement, and decision retrieval across end-to-end KYC onboarding.

Yes, you can generate PDFs and share verification decisions with partners. The API supports session sharing and PDF generation directly, enabling compliant partner data sharing and risk assessment across end-to-end identity verification flows.

Yes, you need an API key to authenticate verification sessions and workflows. The system enforces API-key authentication and includes built-in error handling with rate limits to ensure reliable production use.

To handle rate limits and errors when managing verification sessions, the API includes built-in error handling and rate limiting mechanisms. These features ensure reliable production use across session creation, listing, and deletion operations.

Yes, you can use webhooks for status updates in KYC compliance workflows. The system supports workflow-based gating and webhook integration to manage session statuses and blocklists across identity verification use cases.