When a customer churns, delete their account. The slot is freed immediately and can be filled by the next signup.

```bash
curl -X DELETE "https://context-link.ai/api/v1/api_accounts/tf-cust-8841" \
  -H "Authorization: Bearer $PROVISIONING_TOKEN"
```

```json
{ "status": "deleted", "uid": "tf-cust-8841" }
```

## Request fields

| Field | Type | Description |
|---|---|---|
| `uid` | string | Required, in the path. The customer id you provisioned the account with. An unknown uid is a `404`. |

## Response fields

| Field | Type | Description |
|---|---|---|
| `status` | string | Always `deleted` on a successful call. |
| `uid` | string | The customer id of the account that was destroyed. |

## This is irreversible

Deleting destroys the account and **all** of its connections, posts and chunks. For content you pushed through [custom connections](/docs/white-label/create-connection), Context Link holds the only copy of the indexed text, so back up anything you cannot regenerate from your own database first.

A `404` means there is nothing to delete under that uid, so churn cleanup can treat it as success and retry safely.