[POST] .../v1/chat/edit
Changes the name and/or logo of an existing chat. Use this method to edit editable metadata of an existing standalone chat, such as display name, logo URL or external ID. The request body is required, id must contain the target chat UUID and omitted editable fields are left unchanged by the persistent layer. The current request user must have chat edit permission; linked entity chats may reject direct edits because they inherit ownership from the linked CRM or task entity workflow. Missing body, missing id, denied permission, non-existent chat, linked entity edit restrictions, validation failures and database errors are returned as HTTP 200 ErrorResult business errors.
Request Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| external_id | String | Optional | New external chat ID. |
| id | String | Required | Chat UUID. |
| logo_url | String | Optional | New chat logo URL. |
| name | String | Optional | New chat name. |
Request Example
{
"id": "8cdd646d-dbd0-45c0-8f5b-d90a9b000001",
"name": "Purchase approval team",
"logo_url": "https://example.com/chat-logo.png"
}Response Parameters
| Name | Type | Description |
|---|---|---|
| ok | Boolean | Indicates whether the request completed successfully. |
| result | Update | Update operation result. |
Response Example
{
"ok": true,
"result": {
"row_affected": 1
}
}