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

# Delete Contact

> Soft-delete a team contact.

204 on success. 404 if missing/already deleted. 409 if the contact still
owns a live hub — transfer ownership (or delete the hub)
before removing them; unlike a typical 409, retrying this exact request
will never succeed on its own.

IMPORTANT — hub memberships are NOT preserved for restore:
this severs the contact's login AND cascades their active hub
memberships to 'left' (banned/soft_banned and owned-hub memberships are
left untouched — see the hub_memberships module for the full cascade
contract). POST .../restore reverses the login lock ONLY; it does NOT
reactivate any hub membership the cascade touched. A restored contact
must be explicitly re-added to each hub (POST .../hubs/{hub_id}/members)
to rejoin. This is a deliberate product decision, not a bug.



## OpenAPI

````yaml /openapi/mio-openapi.json delete /api/v1/teams/{team_id}/contacts/{team_contact_id}
openapi: 3.1.0
info:
  description: >-
    Production API reference for Membership.io. Use the authored guides for
    workflows and the generated endpoint pages for exact parameters and schemas.
  title: Membership.io API
  version: 0.1.0
servers:
  - description: Production
    url: https://api.member.dev
security:
  - bearerAuth: []
paths:
  /api/v1/teams/{team_id}/contacts/{team_contact_id}:
    delete:
      tags:
        - contacts-admin
      summary: Delete Contact
      description: |-
        Soft-delete a team contact.

        204 on success. 404 if missing/already deleted. 409 if the contact still
        owns a live hub — transfer ownership (or delete the hub)
        before removing them; unlike a typical 409, retrying this exact request
        will never succeed on its own.

        IMPORTANT — hub memberships are NOT preserved for restore:
        this severs the contact's login AND cascades their active hub
        memberships to 'left' (banned/soft_banned and owned-hub memberships are
        left untouched — see the hub_memberships module for the full cascade
        contract). POST .../restore reverses the login lock ONLY; it does NOT
        reactivate any hub membership the cascade touched. A restored contact
        must be explicitly re-added to each hub (POST .../hubs/{hub_id}/members)
        to rejoin. This is a deliberate product decision, not a bug.
      operationId: >-
        contacts_admin.delete_contacts_admin_delete_teams_by_team_id_contacts_by_team_contact_id
      parameters:
        - in: path
          name: team_id
          required: true
          schema:
            title: Team Id
            type: string
        - in: path
          name: team_contact_id
          required: true
          schema:
            title: Team Contact Id
            type: string
      responses:
        '204':
          description: Successful Response
        '409':
          content:
            application/vnd.api+json:
              schema:
                $ref: '#/components/schemas/JsonApiErrorResponse'
          description: >-
            Contact owns one or more live hubs (code=contact_owns_hub). This is
            NOT resolved by retrying the same request: transfer ownership of
            each listed hub to a different member, or delete the hub itself,
            before removing this contact. The error meta.owned_hub_ids lists the
            affected hubs.
        '422':
          content:
            application/vnd.api+json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
          description: Validation Error
      security:
        - HTTPBearer: []
components:
  schemas:
    JsonApiErrorResponse:
      description: Error JSON:API response.
      properties:
        errors:
          items:
            $ref: '#/components/schemas/JsonApiError'
          title: Errors
          type: array
        meta:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          title: Meta
      required:
        - errors
      title: JsonApiErrorResponse
      type: object
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          title: Detail
          type: array
      title: HTTPValidationError
      type: object
    JsonApiError:
      properties:
        code:
          anyOf:
            - type: string
            - type: 'null'
          title: Code
        detail:
          anyOf:
            - type: string
            - type: 'null'
          title: Detail
        id:
          anyOf:
            - type: string
            - type: 'null'
          title: Id
        meta:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          title: Meta
        source:
          anyOf:
            - additionalProperties:
                type: string
              type: object
            - type: 'null'
          title: Source
        status:
          title: Status
          type: string
        title:
          title: Title
          type: string
      required:
        - status
        - title
      title: JsonApiError
      type: object
    ValidationError:
      properties:
        ctx:
          title: Context
          type: object
        input:
          title: Input
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          title: Location
          type: array
        msg:
          title: Message
          type: string
        type:
          title: Error Type
          type: string
      required:
        - loc
        - msg
        - type
      title: ValidationError
      type: object
  securitySchemes:
    bearerAuth:
      bearerFormat: JWT or mio_sk API key
      description: >-
        Send platform JWTs, contact JWTs, or team API keys as `Authorization:
        Bearer <token>`.
      scheme: bearer
      type: http
    HTTPBearer:
      scheme: bearer
      type: http

````