The Share Session API enables Reusable KYC and KYB — securely sharing verified session data between trusted partner organizations. Works for both User Verification (KYC) and Business Verification (KYB) sessions. The share token encodes theDocumentation Index
Fetch the complete documentation index at: https://docs.didit.me/llms.txt
Use this file to discover all available pages before exploring further.
session_kind so the receiving application reconstructs the same kind when importing.
Endpoints
Share Session
POST /v3/session/{sessionId}/share/ — Generate a time-limited share token for a verified session.Import Shared Session
POST /v3/session/import-shared/ — Import a session shared by a partner using a share token.How it works
Partner A shares a session
After a user completes verification on Partner A’s platform, Partner A calls Share Session with the session ID and the target partner’s application ID. Didit returns a time-limited
share_token.Share token is sent to Partner B
Partner A sends the
share_token to Partner B through their own secure channel (API call, webhook, etc.).Requirements
| Requirement | Details |
|---|---|
| Session status | Only finished sessions ("Approved", "Declined", "In Review") can be shared |
| Partner application ID | The target partner’s application ID (found in Business Console settings) |
| Token TTL | Configurable from 60 seconds to 86,400 seconds (24 hours). Default: 3,600 seconds (1 hour) |
| Authentication | Both partners must authenticate with their own API keys |
Use cases
- Banking → Fintech: A user verified by a bank can access a fintech partner without re-verifying
- Marketplace → Payment provider: Sellers verified on a marketplace can onboard to the payment provider instantly
- Insurance → Healthcare: Cross-industry verification sharing between trusted partners
- Group companies: Share verification data across multiple applications within the same organization
Learn more about the Reusable KYC feature in the Share KYC via API guide.