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

# Update customer

> Every field is optional — only what you send is changed. The questionnaire can be replaced. Email is immutable.

Once the customer is `COMPLETED`, the identity fields verified by the provider are locked and changing any of them returns 409.



## OpenAPI

````yaml api-reference/endl-onboarding-api.json PUT /api/v0/customer/{userId}
openapi: 3.1.0
info:
  title: Endl Partner Onboarding API
  version: '0'
  description: >-
    Onboard end customers for identity verification — individuals (KYC) and
    businesses (KYB) — through one uniform REST surface.


    Authentication is API-key only: every request carries a single `API-KEY`
    header. Unlike the Partner API, responses are **flat** — a successful body
    is the data object itself, with no `{ data, code, message, status }`
    envelope.
servers:
  - url: https://qa-api.endl.xyz
    description: QA
security:
  - apiKey: []
tags:
  - name: Customers
    description: Create, read, update and delete onboarding customers.
  - name: Documents
    description: Upload identity, company and beneficial-owner documents.
paths:
  /api/v0/customer/{userId}:
    parameters:
      - name: userId
        in: path
        required: true
        schema:
          type: string
          format: uuid
        description: Endl's customer id, returned by create.
    put:
      tags:
        - Customers
      summary: Update customer
      description: >-
        Every field is optional — only what you send is changed. The
        questionnaire can be replaced. Email is immutable.


        Once the customer is `COMPLETED`, the identity fields verified by the
        provider are locked and changing any of them returns 409.
      requestBody:
        required: true
        content:
          application/json:
            example:
              firstName: Janet
              phone: '+971511111111'
              questionnaire:
                sections:
                  profileDetails:
                    items:
                      occupation:
                        value: 13-2011
      responses:
        '200':
          description: The updated customer.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Customer'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '409':
          description: A locked identity field was changed after completion.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                code: '409'
                message: >-
                  This customer's KYC is completed; verified identity fields can
                  no longer be changed
                name: PartnerOnboardingUpdate failed to process
components:
  schemas:
    Customer:
      type: object
      properties:
        userId:
          type: string
          format: uuid
        userType:
          type: string
          enum:
            - INDIVIDUAL
            - BUSINESS
        status:
          type: string
          enum:
            - INITIATED
            - PENDING
            - COMPLETED
            - REJECTED
        sumsubApplicantId:
          type: string
        email:
          type: string
        firstName:
          type: string
        lastName:
          type: string
        country:
          type: string
        dateOfBirth:
          type: string
        active:
          type: boolean
        deleted:
          type: boolean
        documents:
          type: array
          items:
            type: object
          description: Populated after uploads.
        questionnaire:
          type: object
          description: The schema plus the answers you submitted.
    Error:
      type: object
      description: >-
        A single problem. `code` is the HTTP status, `message` the specific
        reason, and `name` the operation that failed.
      properties:
        code:
          type: string
        message:
          type: string
        name:
          type: string
    ErrorList:
      type: object
      description: >-
        Several problems at once. Returned by validation failures; nothing is
        created or changed.
      properties:
        errors:
          type: array
          items:
            $ref: '#/components/schemas/Error'
  responses:
    BadRequest:
      description: >-
        Validation failed. Nothing is written. One problem returns a flat
        object; several return an `errors` array.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorList'
          example:
            errors:
              - code: '400'
                message: firstName is required
                name: PartnerOnboardingCreate failed to process
              - code: '400'
                message: country must be an ISO 3166-1 alpha-3 code (e.g. ARE)
                name: PartnerOnboardingCreate failed to process
    Unauthorized:
      description: Missing or invalid `API-KEY`.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            code: '401'
            message: Authentication Failed!
            name: PartnerOnboarding failed to process
    Forbidden:
      description: >-
        The key lacks the `onboarding` permission, the customer belongs to
        another partner, or onboarding is not permitted for that country.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            code: '403'
            message: Onboarding is not permitted for this country
            name: PartnerOnboardingCreate failed to process
    NotFound:
      description: Customer or owner not found. A deleted customer also returns 404.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            code: '404'
            message: Not found
            name: PartnerOnboardingGet failed to process
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: API-KEY
      description: Your partner API key. The key must carry the `onboarding` permission.

````