Source: https://datafa.st/docs/api/account/notes/delete
Markdown source: https://datafa.st/docs/api/account/notes/delete.md
Description: Permanently delete one manual chart note.

# Delete note

`DELETE https://datafa.st/api/v1/admin/websites/{websiteId}/notes/{noteId}`

Permanently delete one manual chart note.

Required account-token permission: `notes:write`.

## Parameters

`websiteId` and `noteId` are required path parameters. No body is needed. Only the manual note in the selected website is deleted; this endpoint cannot delete social mentions.

The response contains `data: [{ "id": "...", "deleted": true }]`. A missing/already-deleted note returns `404`.

MCP: `datafast_notes_delete`. The agent must confirm the exact note with the user, then pass `confirm: true`. Without confirmation, the MCP tool returns a preview and does not delete anything.

## Authentication

Use `Authorization: Bearer df_...` for one website, or `dft_...` with the required permission and website access. Notes always require `websiteId` in the path. Mention reads infer it from a website key; account tokens must provide the `websiteId` query parameter.

Existing website keys and `*` account tokens work automatically. For restricted account tokens, open [Account settings → API](/dashboard/settings?tab=api), expand your token, choose **Edit permissions**, and enable **Notes → Read / Write**. Save permissions to keep the same token and MCP connection. Only the signed-in token owner can edit permissions in the dashboard; no API or MCP operation can do this.

## Errors

Standard errors use `{ "status": "error", "error": { "code": 400, "message": "..." } }`. Expect `400` for invalid fields, dates, or IDs; `401` for invalid credentials; `403` for missing permissions or website access; `404` for a missing website/note; `409` for reusing a creation key with different input; and `429` for the normal API rate limit.

## Code examples

### Example request

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

### Success response

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