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

# Delete a User

> Delete a user from your platform.

This is a **soft delete** — we mark the user as deleted, but their full
record stays in our system for your history and audit trail. Nothing is
permanently erased. After this call the user no longer appears in your
user list and can't be used for anything new.

The user's email becomes free to use again straight away, so you can add a
new user with the same email later if you need to. That new user will be a
separate record with its own ID and its own wallet — the old user's history
stays linked to the old ID.

You can safely call this more than once. Deleting a user who is already
deleted simply succeeds and changes nothing.



## OpenAPI

````yaml DELETE /v1/platform/users/{user_id}
openapi: 3.1.0
info:
  title: Finogate Platform API v1
  version: 0.1.0
servers:
  - url: https://api-sandbox.finogates.com
    description: Sandbox
  - url: https://api.finogates.com
    description: Production
security: []
tags:
  - name: auth
  - name: users
  - name: payees
  - name: verification
  - name: bank accounts
  - name: card processing
  - name: digital-assets
  - name: international
  - name: onboarding
  - name: pending-applications
  - name: wallets
  - name: payments
  - name: catalog
  - name: webhooks
  - name: phone-numbers
  - name: sms
  - name: calls
  - name: listings
  - name: embed-tokens
paths:
  /v1/platform/users/{user_id}:
    delete:
      tags:
        - users
      summary: Delete a User
      description: >-
        Delete a user from your platform.


        This is a **soft delete** — we mark the user as deleted, but their full

        record stays in our system for your history and audit trail. Nothing is

        permanently erased. After this call the user no longer appears in your

        user list and can't be used for anything new.


        The user's email becomes free to use again straight away, so you can add
        a

        new user with the same email later if you need to. That new user will be
        a

        separate record with its own ID and its own wallet — the old user's
        history

        stays linked to the old ID.


        You can safely call this more than once. Deleting a user who is already

        deleted simply succeeds and changes nothing.
      operationId: deactivate_user_v1_platform_users__user_id__delete
      parameters:
        - name: user_id
          in: path
          required: true
          schema:
            type: string
            format: uuid
            description: The unique ID of the user you want to delete.
            examples:
              - b3a9b622-cc63-4d3c-aad6-2d8e29e6f9d4
            title: User Id
          description: The unique ID of the user you want to delete.
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CommonResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - _AuthenticatedBearer: []
components:
  schemas:
    CommonResponse:
      properties:
        status_code:
          type: integer
          title: Status Code
          description: HTTP status code for the response.
        data:
          title: Data
          description: Payload or error details.
        query_generated_time:
          type: integer
          title: Query Generated Time
          description: >-
            UTC timestamp (milliseconds since epoch) when response was
            generated.
      type: object
      required:
        - status_code
        - data
        - query_generated_time
      title: CommonResponse
      description: |-
        Standard response wrapper for single-object responses and errors.

        Generic over the payload type. A route that declares
        ``CommonResponse[SomeModel]`` gets the real ``data`` schema rendered in
        OpenAPI/Swagger; a bare ``CommonResponse`` leaves ``data`` untyped.
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    _AuthenticatedBearer:
      type: oauth2
      flows:
        password:
          scopes: {}
          tokenUrl: /v1/platform/auth/token

````