Skip to main content
PATCH
Actualizar una nota
Updates a note in place. Only content and type can change — a note cannot be moved to a different contact or ticket after creation.

Endpoint

Required scope

crm:notes:write

Headers

Path parameters

Body

All fields optional. Send only what changes.

Example request

Response

200 OK

Returns the updated note, same shape as GET /v1/crm/notes/:id.

400 Bad Request

Empty content, content longer than 5000 characters, a type outside the allowed set, or a property the endpoint does not accept — including chat_user and ticket_id, which are immutable after creation.

401 Unauthorized

Missing, invalid, revoked, or expired token.

403 Forbidden

The token does not have the crm:notes:write scope.

404 Not Found

No note with that id, or the note belongs to a different company.

Operational notes

  • created_by does not change on edit. The note keeps its original author even when a different token rewrites the text, so an edited note can misattribute who said what. Post a new note instead of rewriting someone else’s.
  • Attachment is fixed. To move a note to another ticket, delete it and create a new one.

Authorizations

Authorization
string
header
required

Personal Access Token con prefijo kbai_pk_. Generar desde el portal con permiso developer.manage_tokens.

Path Parameters

id
string
required

Body

application/json
content
string
type
enum<string>
Available options:
note,
call,
email,
meeting

Response

200 - application/json
note
object
required