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

# delete avatar

> Delete an avatar by ID. By default this is a soft delete: the avatar disappears from Lab and the API, which can't restore it, and its stored assets are kept. Pass `hard=true` to permanently purge the avatar and its stored assets (source image and generated versions). A hard delete cannot be undone and is intended for data-erasure requests; it also purges avatars that were previously soft-deleted. Stored assets are kept while another avatar still uses them, such as a copy Anam made for another organization. Deleting the last avatar that uses them starts the purge, which runs after the response and is best effort. A hard delete never deletes personas: when active personas (or their drafts) still use the avatar the request fails with `409 Conflict` and the impacted persona IDs. Move those personas to another avatar (e.g. `PUT /v1/personas/{id}` with a new `avatarId`) and retry.



## OpenAPI

````yaml https://api.anam.ai/swagger.json delete /v1/avatars/{id}
openapi: 3.1.0
info:
  title: Anam AI API
  version: '1.0'
servers:
  - url: https://api.anam.ai
    description: Anam API
security:
  - BearerAuth: []
tags:
  - name: Sessions
  - name: Avatar Videos
  - name: Meetings
  - name: Personas
  - name: Avatars
  - name: Voices
  - name: Pronunciation Dictionaries
  - name: LLMs
  - name: Knowledge
  - name: Tools
  - name: Share Links
  - name: Engine
paths:
  /v1/avatars/{id}:
    delete:
      tags:
        - Avatars
      summary: delete avatar
      description: >-
        Delete an avatar by ID. By default this is a soft delete: the avatar
        disappears from Lab and the API, which can't restore it, and its stored
        assets are kept. Pass `hard=true` to permanently purge the avatar and
        its stored assets (source image and generated versions). A hard delete
        cannot be undone and is intended for data-erasure requests; it also
        purges avatars that were previously soft-deleted. Stored assets are kept
        while another avatar still uses them, such as a copy Anam made for
        another organization. Deleting the last avatar that uses them starts the
        purge, which runs after the response and is best effort. A hard delete
        never deletes personas: when active personas (or their drafts) still use
        the avatar the request fails with `409 Conflict` and the impacted
        persona IDs. Move those personas to another avatar (e.g. `PUT
        /v1/personas/{id}` with a new `avatarId`) and retry.
      operationId: deleteAvatar
      parameters:
        - in: path
          name: id
          schema:
            type: string
            format: uuid
          required: true
          description: Avatar ID
        - in: query
          name: hard
          schema:
            type: boolean
          required: false
          description: >-
            When `true`, permanently deletes the avatar and purges its stored
            source and generated assets instead of soft-deleting it.
      responses:
        '200':
          description: Successfully deleted avatar
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    example: Avatar deleted successfully
        '400':
          description: Bad request - Invalid avatar ID
        '401':
          description: Unauthorized - Invalid or missing API key
        '403':
          description: Forbidden - API key lacks the required permission
        '404':
          description: Not Found - Avatar not found
        '409':
          description: >-
            Conflict - the avatar is still used by active personas (hard delete
            only). Reassign those personas to another avatar, then retry.
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                    example: >-
                      Avatar is used by active personas. Move them to another
                      avatar before hard-deleting it.
                  impactedPersonaIds:
                    type: array
                    items:
                      type: string
                      format: uuid
        '500':
          description: Server error
        '503':
          description: >-
            The API key could not be checked because of a temporary server
            problem. The key may be valid; retry after `Retry-After` seconds.
          headers:
            Retry-After:
              description: Seconds to wait before retrying.
              schema:
                type: integer
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceUnavailableError'
components:
  schemas:
    ServiceUnavailableError:
      type: object
      required:
        - error
        - message
      properties:
        error:
          type: string
          example: Service temporarily unavailable
        message:
          type: string
          example: We could not check your API key. Please retry shortly.
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.