> ## 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.

# Tombstone a device with POST

> Tombstone a device when a client cannot send DELETE.

Tombstone a device when a client cannot send DELETE.

## Request

<ParamField path="did" type="string" required>
  The DID that owns the device.
</ParamField>

<ParamField path="deviceId" type="string" required>
  The device identifier.
</ParamField>

<RequestExample>
  ```bash Request theme={null}
  curl --request POST \
    --url "https://directory.example.com/dids/did%3Atalaria%3A1111111111111111111111/devices/mobile-01/tombstone"
  ```
</RequestExample>

## Response

<ResponseField name="status" type="string" required>
  The submission status.
</ResponseField>

<ResponseField name="did" type="string" required>
  The DID affected by the request.
</ResponseField>

<ResponseField name="extrinsic" type="string" required>
  The public operation name.
</ResponseField>

<ResponseField name="tx_hash" type="string" required>
  The submitted transaction hash.
</ResponseField>

<ResponseField name="message" type="string" required>
  A human-readable submission result.
</ResponseField>

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

<Note>
  This compatibility route has the same effect as the `DELETE` device route. The request body is optional.
</Note>