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

# Deactivate a DID

> Permanently mark a Talaria identity as inactive

Deactivation is the identity-level retirement operation. After it settles, compatible clients should stop treating the DID as an active message recipient or current signing identity.

<Warning>
  Deactivation is intentionally permanent. Do not use it for a temporarily offline device. Tombstone or remove only the affected device instead.
</Warning>

## Request

<ParamField path="did" type="string" required>
  The DID to deactivate.
</ParamField>

The request body is optional. If supplied, `did` must match the path.

<RequestExample>
  ```bash Request theme={null}
  curl --request POST \
    --url "https://directory.example.com/dids/did%3Atalaria%3A1111111111111111111111/deactivate" \
    --header "Content-Type: application/json" \
    --data '{"did":"did:talaria:1111111111111111111111"}'
  ```
</RequestExample>

## Response

<ResponseExample>
  ```json 202 Response theme={null}
  {
    "status": "accepted",
    "did": "did:talaria:1111111111111111111111",
    "extrinsic": "deactivate_did",
    "tx_hash": "<transaction-hash>",
    "message": "Chain extrinsic submitted"
  }
  ```
</ResponseExample>

After final settlement, `GET /resolve/{did}` returns `"deactivated": true`.

## Straight to the point

```http theme={null}
POST /dids/{did}/deactivate
```

* Permanent identity lifecycle change
* Accepted: `202`
* Verify later with `GET /resolve/{did}`