Skip to main content
PATCH
Required token scopes: Edit and delete notes of all chats The original author stays as it is. Your API token becomes the note’s lastEditor, with customName when you send one. Sending the same text as the saved text changes nothing and returns the note as it is. The editor name can change only together with the text: the same text with a different customName returns 400.

Authorizations

Authorization
string
header
required

API token generated in Texter: gear icon → Developers → API Tokens. When creating a token, assign it the scopes required by the endpoints you plan to call - each endpoint lists its required scopes.

Path Parameters

chatId
string
required

The unique identifier of the chat. You can obtain this value by using the Search Chats endpoint with the contact's phone number

noteId
string
required

The unique identifier of the note (_id). You can obtain it from List Chat Notes or from the response of Create Chat Note

Body

application/json
text
string
required

The new note text, up to 4096 characters

Maximum string length: 4096
customName
string

Editor name shown in the inbox instead of the default. Up to 50 characters, must contain a visible character

Maximum string length: 50

Response

The updated note

An internal note on a chat

_id
string
required

Unique note ID

Example:

"6731f0c2a1b2c3d4e5f60718"

chatId
string
required

ID of the chat the note belongs to

Example:

"67a87067aeed4dee1271cb4d"

text
string
required

The note text

author
object
required

Who wrote the note. Kept as it is on every edit

createdAt
integer
required

Creation time, Unix milliseconds

Example:

1762851000000

updatedAt
integer
required

Last change time, Unix milliseconds

Example:

1762851000000

messageId
string

ID of the chat message the note is attached to. Missing when the chat had no messages

lastEditor
object

Who made the last text edit. Missing on notes that were never edited