> ## Documentation Index
> Fetch the complete documentation index at: https://docs.didit.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Share Session (Reusable KYC)

> Reusable KYC and KYB — share verified sessions across trusted partners with time-limited tokens. Skip re-verification, cut friction, save costs.

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 the `session_kind` so the receiving application reconstructs the same kind when importing.

## Endpoints

<CardGroup cols={2}>
  <Card title="Share Session" icon="share-nodes" href="/sessions-api/share-session/share">
    `POST /v3/session/{sessionId}/share/` — Generate a time-limited share token for a verified session.
  </Card>

  <Card title="Import Shared Session" icon="download" href="/sessions-api/share-session/import">
    `POST /v3/session/import-shared/` — Import a session shared by a partner using a share token.
  </Card>
</CardGroup>

## How it works

<Steps>
  <Step title="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`.
  </Step>

  <Step title="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.).
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 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

<Note>
  Learn more about the Reusable KYC feature in the [Share KYC via API guide](/core-technology/reusable-kyc/share-kyc-via-api).
</Note>