Source: https://datafa.st/docs/api/account/website-keys/delete
Markdown source: https://datafa.st/docs/api/account/website-keys/delete.md
Description: Revoke a df_ website API key.

# Delete website key

`DELETE https://datafa.st/api/v1/admin/websites/{websiteId}/apikeys/{apiKeyId}`

Revoke a `df_` website API key permanently. Active integrations using the key will receive **401** responses.

## Request

#### Path parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `websiteId` | string | — | Website ObjectId. From [List websites](/docs/api/account/websites/list) (`_id` field). Example: `665f0b3c4d2e1a0012345678`. |
| `apiKeyId` | string | — | Website API key ObjectId from [List website keys](/docs/api/account/website-keys/list). |

## Response

Returns a JSON object with `status: "success"` and endpoint-specific fields in `data`.

#### Response fields

| Field | Type | Description |
| --- | --- | --- |
| `data[].deleted` | boolean | True when the resource was deleted. |

### Authentication

Use a `dft_` account token with `api-keys:write`.

A `df_` website API key for the same website can also call this route when the path `websiteId` matches the key's website. Write access with a `df_` key is capped at **member** level — owner-only actions such as [team management](/docs/api/account/team) require a `dft_` token and owner role.

### Errors

See [API errors](/docs/api#errors) for the standard error envelope, auth failures, validation errors, permission errors, and rate limits.

## Code examples

### Example request

```bash
curl -X DELETE "https://datafa.st/api/v1/admin/websites/{websiteId}/apikeys/{apiKeyId}" \
  -H "Authorization: Bearer dft_xxx"
```

### Success response

```json
{
  "status": "success",
  "data": [{
    "deleted": true
  }]
}
```