# Add a note to a lead

> Write a note on a lead's timeline, such as what was said on a call or the next step. Your team and your Revnu agent read it on the lead.

Canonical: https://revnu.com/docs/lead-notes
Last updated: 2026-10-30

```bash
curl -X POST -H "Authorization: Bearer $REVNU_API_TOKEN" \
  -H "content-type: application/json" \
  -d '{"body":"Call went well. They want a proposal for 20 seats by Friday."}' \
  https://revnu.com/api/v1/leads/sn7…/notes
```

## Body

`{ "body": "…" }`: the note, up to 4,000 characters. Any other field is a `400`.

## Response

`201 { "note": { id, kind, body, deal, author, authorName, source, createdAt, editedAt } }`. `kind` is `note`, `author` is `api` and `authorName` is your token's label. `404` for an unknown or another account's lead.

Read notes back on [`GET /leads/{id}`](https://revnu.com/docs/lead.md), newest first, with the deal's stage changes between them.

## Frequently asked questions

### Does Revnu act on what a note says?

The agent reads notes as information about the lead, never as instructions. To ask it to do something, send a [message](https://revnu.com/docs/agent-messages.md).

### Can I edit or delete a note through the API?

Not yet. Your team edits and deletes their own notes in the dashboard, and your Revnu agent its own.

### Which scope does this need?

`leads:write`. A token without it gets `403` with `requiredScope` in the body.