Source: https://datafa.st/docs/api/account/access-tokens/delete
Markdown source: https://datafa.st/docs/api/account/access-tokens/delete.md
Description: Revoke one dft_ account token.

# Delete access token

`DELETE https://datafa.st/api/v1/admin/access-tokens/{tokenId}`

Revoke one `dft_` account token permanently. You can only delete tokens you created.

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

## Request

#### Path parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `tokenId` | string | — | Access token ObjectId from [List access tokens](/docs/api/account/access-tokens/list). |

## Response

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

#### Response fields

| Field | Type | Description |
| --- | --- | --- |
| `data[].message` | string | Human-readable confirmation or status message for the operation. |

### Authentication

Requires a `dft_` account token with `api-keys:write`. Website API keys (`df_`) cannot call this endpoint because it manages account-level resources.

Create tokens in [Account settings → API](https://datafa.st/dashboard/settings?tab=api).

### Errors

**403** — Called with a `df_` website key.

**404** — Token not found or not owned by the caller.

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/access-tokens/{tokenId}" \
  -H "Authorization: Bearer dft_xxx"
```

### Success response

```json
{
  "status": "success",
  "data": [{
    "message": "Access token deleted successfully"
  }]
}
```
