---
title: "delete avatar"
method: DELETE
path: "/v1/avatars/{id}"
tags: ["Avatars"]
---

# delete avatar

`DELETE /v1/avatars/{id}`

Delete an avatar by ID. By default this is a soft delete: the avatar is hidden and can be restored. 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. 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.

## Path parameters

- `id` string, uuid, required

## Query parameters

- `hard` boolean

## Response `200`

Successfully deleted avatar

- object
  - `message` string

## Other responses

- `400` — Bad request - Invalid avatar ID
- `401` — Unauthorized - Invalid or missing API key
- `403` — Forbidden - API key lacks the required permission
- `404` — Not Found - Avatar not found
- `409` — Conflict - the avatar is still used by active personas (hard delete only). Reassign those personas to another avatar, then retry.
- `500` — Server error

---

[API](https://skmtc.net/anam/apis/anam-ai-api.md) · [All operations](https://skmtc.net/anam/apis/anam-ai-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/anam/anam-ai-api/versions/67afd1c5db59/schema)