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

# Upsert a customer

> Creates or updates a customer and syncs them to the core banking engine. Returns the `customerId` to use everywhere else.



## OpenAPI

````yaml /api-reference/openapi.json post /v1/kyc/customers
openapi: 3.1.0
info:
  title: Bridge API
  version: 1.0.0
  description: >-
    Bridge is Banking-as-a-Service: launch wallets, lending, and payment
    collections while a bank/FSP retains custody and compliance. This reference
    covers the production-proven surface. Get a `keyId`/`secret` from the
    Dashboard, exchange them at `/generate-token` for a 1-hour Bearer token,
    then call the product APIs.


    **Auth recovery:** tokens expire after ~1h. On a 401, re-call
    `/generate-token` and retry once.
servers:
  - url: https://{baasHost}/api
    description: BaaS core (KYC, Lending, Wallets)
    variables:
      baasHost:
        default: services.finance.reli.co.tz
  - url: https://{gatewayHost}/api
    description: >-
      Collections gateway (payment collection) — a separate service and key from
      the BaaS core.
    variables:
      gatewayHost:
        default: bridge-fsp.usereli.tech
security:
  - bearerAuth: []
tags:
  - name: Auth
    description: Exchange API keys for a Bearer token.
  - name: KYC
    description: Customers and identity. KYC is the authoritative customer store.
  - name: Lending
    description: Loan products, origination, schedules, and repayments.
  - name: Wallets
    description: Stored-value wallets, deposits, and escrow.
  - name: Collections
    description: Mobile (USSD) payment collection. Separate service + key.
paths:
  /v1/kyc/customers:
    post:
      tags:
        - KYC
      summary: Upsert a customer
      description: >-
        Creates or updates a customer and syncs them to the core banking engine.
        Returns the `customerId` to use everywhere else.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UpsertCustomerRequest'
            example:
              legalName: Jane Doe
              type: PERSON
              mobile: '+255700000000'
              email: jane@example.com
              dob: '1995-01-10'
              nationalId: NID12345
      responses:
        '200':
          description: Customer upserted
          content:
            application/json:
              example:
                customerId: aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee
                legalName: Jane Doe
                type: PERSON
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    UpsertCustomerRequest:
      type: object
      required:
        - legalName
        - type
      properties:
        customerId:
          type: string
          format: uuid
          description: Omit to create; include to update.
        legalName:
          type: string
        type:
          type: string
          enum:
            - PERSON
            - BUSINESS
        mobile:
          type: string
        email:
          type: string
          format: email
        dob:
          type: string
          description: yyyy-MM-dd
        nationalId:
          type: string
        address:
          type: object
          additionalProperties: true
  responses:
    Unauthorized:
      description: Missing/expired token. Re-call /generate-token and retry once.
      content:
        application/json:
          example:
            error:
              code: UNAUTHORIZED
              message: Token expired or invalid
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        Bearer token from POST /generate-token. Expires ~1h; on 401, re-generate
        and retry once.

````