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

# Send User KYC Data (v1)

> Share User KYC PII details

Note: KYC Sharing works on a reliance model where you are liable to complete the KYC based on the discussed parameters and share the PII data of approved end-users. This includes two steps:

1. Share Data (including legal name, document number etc.)
    
2. Share Supporting Documents




## OpenAPI

````yaml /openapi-v1.json post /api/v1/user/client_user/kyc
openapi: 3.1.0
info:
  title: Saber Money API (v1)
  version: v1
  description: >-
    ## Authentication


    There is no standalone API-key auth — every request must be **signed**. An
    API key by itself authenticates nothing. Each call requires four headers
    together: `X-Api-Key` (your key), `X-Signature` (HMAC-SHA256 of `apiKey +
    timestamp` — or `apiKey + timestamp + userId` when `X-User-Id` is required —
    keyed with your API secret), `X-Timestamp` (unix seconds), and
    `X-Request-Id` (any unique string per request). The signature must be
    computed by a client script; there is no way to derive it by hand. Use the
    HMAC Generator flow to compute valid values for manual testing.


    ## Common Authentication Errors


    - **Invalid Client ID**: {"error_code":6092,"message":"X-Client-Id
    invalid","success":false}

    - **Invalid Secret**: {"error_code":6090,"message":"invalid
    secret","success":false}

    - **Timestamp (Older than 10 secs)**:
    {"errors":{"error_code":6093,"text":"timestamp expired"},"success":false}
servers:
  - url: https://api.saber.money
security: []
paths:
  /api/v1/user/client_user/kyc:
    post:
      tags:
        - KYC and EDD Operations
      summary: Send User KYC Data (v1)
      description: >
        Share User KYC PII details


        Note: KYC Sharing works on a reliance model where you are liable to
        complete the KYC based on the discussed parameters and share the PII
        data of approved end-users. This includes two steps:


        1. Share Data (including legal name, document number etc.)
            
        2. Share Supporting Documents
      operationId: send-user-kyc-data-v1
      parameters:
        - name: X-Api-Key
          in: header
          required: true
          description: Your API key (configured in credentials)
          schema:
            type: string
        - name: X-Signature
          in: header
          required: true
          description: >-
            HMAC-SHA256 signature (auto-generated) To test manually: HMAC-SHA256
            of `apiKey + timestamp` (or `apiKey + timestamp + userId` when
            X-User-Id is required), keyed with your API secret. The HMAC
            Generator flow computes this for you.
          schema:
            type: string
        - name: X-Timestamp
          in: header
          required: true
          description: >-
            Unix timestamp in seconds (auto-generated) Unix seconds, e.g.
            `Math.floor(Date.now() / 1000)`. Must match the timestamp used in
            the X-Signature computation.
          schema:
            type: string
        - name: X-Request-Id
          in: header
          required: true
          description: >-
            Unique request identifier (auto-generated) Any unique string per
            request, e.g. a UUID.
          schema:
            type: string
        - name: X-User-Id
          in: header
          required: true
          description: User UUID (set above)
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                email:
                  type: string
                  description: The email field
                phone:
                  type: string
                  description: The phone field
                legal_name:
                  type: string
                  description: The legal_name field
                poa:
                  type: string
                  description: The poa field
                poi:
                  type: string
                  description: The poi field
                country_iso3:
                  type: string
                  description: The country_iso3 field
              required:
                - legal_name
            example:
              legal_name: John Doe
              poa: required
              poi: required
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  data:
                    type: object
                    properties:
                      status:
                        type: string
              example:
                success: true
                data:
                  status: Verified

````

## Related topics

- [Send User KYC Documents (v1)](/api-reference/kyc-and-edd-operations/send-user-kyc-documents-v1.md)
- [Reset KYC [SANDBOX ONLY] (v1)](/api-reference/kyc-and-edd-operations/reset-kyc-[sandbox-only]-v1.md)
- [Get User Details (v1)](/api-reference/user-operations/get-user-details-v1.md)
- [Get EDD Request (v1)](/api-reference/kyc-and-edd-operations/get-edd-request-v1.md)
- [List EDD Requests (v1)](/api-reference/kyc-and-edd-operations/list-edd-requests-v1.md)