Source: https://datafa.st/docs/api/account/notes
Markdown source: https://datafa.st/docs/api/account/notes.md
Description: Read and manage timestamped notes on your website’s chart.

# Manual notes

Record what changed so you can connect your work with traffic and revenue later.

- [List or search notes](/docs/api/account/notes/list) — `notes:read`
- [Create a note](/docs/api/account/notes/create) — `notes:write`
- [Update a note](/docs/api/account/notes/update) — `notes:write`
- [Delete a note](/docs/api/account/notes/delete) — `notes:write`

For example, ask your agent “Add a note that we launched the new landing page today.” In your agent or CI workflow, you can also record significant marketing deployments automatically; use the commit SHA as the creation key to prevent duplicate retries. DataFast records the note; the external workflow decides which commits qualify.

MCP tools: `datafast_notes_list`, `datafast_notes_create`, `datafast_notes_update`, and `datafast_notes_delete`. [Connect your agent](/docs/mcp-introduction).

## Response

`data` is an array of manual notes. Each note includes `id`, `websiteId`, `text`, `timestamp` (UTC ISO), `author` (`id`, `name`, `image`, or null if the author was deleted), `createdAt`, and `updatedAt`. The author is derived from the authenticated account; it cannot be supplied by the caller.

API-created notes appear on the existing dashboard chart at their timestamp. They remain visible when changing the chart's period or granularity, subject to the chart's note visibility toggle. Manual notes are private to authorized website users; public dashboard responses do not expose them.

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