---
title: "Update Note"
method: PUT
path: "/v1.0/notes/{noteId}"
tags: ["Notes"]
---

# Update Note

`PUT /v1.0/notes/{noteId}`

Updates the content and pin state of an existing note.

Notes:
- content must not be blank; isPin must not be null.
- content is silently truncated to 2000 characters.
- If leadId is supplied in the body, it must match the note's lead; otherwise 400 INVALID_UPDATE_OPERATION_LEADID.
- Caller must have access to the lead; otherwise 404 LEAD_NOT_EXIST.
- The response body is empty.

## Path parameters

- `noteId` integer, required

## Headers

- `Authorization` string, required
- `Content-Type` string, required

## Request body

- NoteRequest — Note payload.
  - `content` string, required — Note content. Silently truncated to 2000 characters.
  - `leadId` integer, required — ID of the lead this note belongs to. Must be accessible to the caller.
  - `isPin` boolean, required — Whether to pin this note to the top of the lead's timeline.

## Response `200`

Note updated successfully. No response body.

## Other responses

- `400` — Missing or invalid parameter (20012 INVALID_PARAMETER), or the supplied leadId does not match the note's lead (INVALID_UPDATE_OPERATION_LEADID).
- `401` — Missing or invalid authentication token.
- `404` — Note does not exist (20007 RESOURCE_NOT_EXIST) or lead is not accessible (20006 LEAD_NOT_EXIST).
- `500` — Internal server error.

---

[API](https://skmtc.net/lofty/apis/lofty-service-open-apis.md) · [All operations](https://skmtc.net/lofty/apis/lofty-service-open-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lofty/lofty-service-open-apis/versions/23e640467118/schema)