Skip to main content
The Share Session API enables Reusable KYC — securely sharing verified user data between trusted partner organizations. When a user is verified on one platform, their verification can be shared with a partner, eliminating the need for re-verification.

​
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

1

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

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.).
3

Partner B imports the session

Partner B calls Import Shared Session with the share_token. Didit creates a copy of the verified session in Partner B’s account with full verification data.

​
Requirements

RequirementDetails
Session statusOnly finished sessions ("Approved", "Declined", "In Review") can be shared
Partner application IDThe target partner’s application ID (found in Business Console settings)
Token TTLConfigurable from 60 seconds to 86,400 seconds (24 hours). Default: 3,600 seconds (1 hour)
AuthenticationBoth 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.