Actualizar una nota
Notes
PATCH /v1/crm/notes/:id
Edit a note’s text or interaction type.
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 asGET /v1/crm/notes/:id.
400 Bad Request
Emptycontent, 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 thecrm:notes:write scope.
404 Not Found
No note with that id, or the note belongs to a different company.Operational notes
created_bydoes 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
Personal Access Token con prefijo kbai_pk_. Generar desde el portal con permiso developer.manage_tokens.
Path Parameters
Response
200 - application/json