Import Shared Session
Redeem a share token to clone a KYC or KYB session into the calling application with a fresh session_id. Not idempotent — a token redeems once per receiver.
KYC and KYB support
Didit decodes the share token, reads the embeddedsession_kind, and clones the corresponding kind of session:
session_kind: "user"— clones the user session plus its related identity, face, liveness, face-match, AML, location, POA, phone, email, database-validation, and log rows.session_kind: "business"— clones the business session plus its related registry check, key-people records, documents, AML screenings, phone, email, location, questionnaire, and log rows.
session_kind field, Didit defaults to "user" for backward compatibility.
What gets created
- A new session of the same kind in your application with a fresh
session_id,session_number, andsession_url. - The new session’s
shared_from_sessionfield points at the original session in the source application. - The new session’s status is either the original status (
trust_review: true) orIN_REVIEW(trust_review: false). - A new entity (User or Business) is auto-created for the
vendor_dataif one doesn’t exist.
Examples
- Import a User Verification (KYC) session
- Import a Business Verification (KYB) session
trust_review parameter
Errors
Idempotency
Importing the sameshare_token twice is rejected with 403 — the duplicate-import check runs against both user and business tables depending on session_kind.
Related
Authorizations
Body
JWT share token issued by POST /v3/session/{sessionId}/share/.
"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
If true, the cloned session keeps the source's final status. If false, it is forced into In Review.
false
UUID of a workflow in the calling application. Cross-application IDs are rejected with 404.
"9f9b1234-aaaa-bbbb-cccc-1234567890ab"
Optional override for the cloned session's vendor_data.
"user-1"
Response
Session cloned. The body is the V3 decision payload for both kinds, discriminated by session_kind: "user" (KYC) with list-based feature blocks such as id_verifications, liveness_checks, aml_screenings; "business" (KYB) with blocks like registry_checks and key_people_checks. Both include shared_from_session — the session_id of the original session in the source application. With trust_review: false the cloned session's status is forced to In Review.