# Delete client

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /client:
    delete:
      summary: Delete client
      deprecated: false
      description: Permanently remove a client from the workspace.
      tags:
        - Client Access
      parameters: []
      requestBody:
        content:
          application/json:
            schema:
              type: object
              required:
                - workspace_id
                - client_id
              properties:
                workspace_id:
                  type: string
                  examples:
                    - 65f99a0dd96fae8ab61130c0
                client_id:
                  type: string
                  examples:
                    - 70218d5e05561a3877dcb77f
              x-apidog-orders:
                - workspace_id
                - client_id
              x-apidog-ignore-properties: []
      responses:
        '200':
          description: Deleted
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GenericSuccessResponse'
              example:
                status: success
          headers: {}
          x-apidog-name: OK
      security:
        - ApiKeyAuth: []
          x-apidog:
            schemeGroups:
              - id: 5106IVJ-uBj-Hex3jmid1
                schemeIds:
                  - ApiKeyAuth
            required: true
            use:
              id: 5106IVJ-uBj-Hex3jmid1
            scopes:
              5106IVJ-uBj-Hex3jmid1:
                ApiKeyAuth: []
      x-apidog-folder: Client Access
      x-apidog-status: released
      x-run-in-apidog: https://app.apidog.com/web/project/929054/apis/api-24563841-run
components:
  schemas:
    GenericSuccessResponse:
      type: object
      properties:
        status:
          type: string
          examples:
            - success
      x-apidog-orders:
        - status
      x-apidog-ignore-properties: []
      x-apidog-folder: ''
  securitySchemes:
    ApiKeyAuth:
      type: apikey
      in: header
      name: x-api-key
      description: |
        API key issued in the PlusVibe dashboard. The server reads it
        from the `x-api-key` header and injects it into the request as
        the `api_key` query parameter, which is why you will see
        `api_key` referenced in validation errors.
    apiKey:
      type: apikey
      in: body
      name: api_key
      description: API key passed in request body
servers:
  - url: https://api.plusvibe.ai/api/v1
    description: Prod Env
security:
  - ApiKeyAuth: []
    x-apidog:
      schemeGroups:
        - id: uS5KiuC4wfZHK42AzOfA_
          schemeIds:
            - ApiKeyAuth
      required: true
      use:
        id: uS5KiuC4wfZHK42AzOfA_
      scopes:
        uS5KiuC4wfZHK42AzOfA_:
          ApiKeyAuth: []

```