Update Group Information

Overview

Update a group conversation's display information - name, description, avatar image URL, and optional metadata. Use this from the SDK group profile or settings screen when an admin or permitted member edits group details.

Only the fields you send are updated; omit fields you want to leave unchanged. The response returns the full updated conversation document.

When to use this endpoint?

Use Update Group Information when:

A user renames the group from the SDK header or info panel.
You update the group description or avatar after branding changes.
You sync metadata from an external workspace (project id, channel slug, and so on).
You save changes from a group edit form after loading conversation details.

Part of the Chat Conversation APIs for the chat package / SDK — not Platform → Conversations. Requires a chat user Bearer token; editing may be restricted when onlyAdminCanEditInfo is true.

Request Fields

Field	Type	Required	Description
conversationId	string	Required	The group conversation's `_id`.
groupName	string	Optional	New display name for the group in the SDK conversation list and header.
groupDescription	string	Optional	Updated description shown in group info screens.
groupImage	string	Optional	URL for the group avatar. Upload the image to your CDN or storage first, then pass the public URL here.
metadata	object	Optional	Arbitrary key-value map merged or replaced per your API behavior - use for app-specific group attributes.

PATCH{baseUrl}/api/{apiVersion}/conversation/group/information/update

Authentication: Required (Bearer token)
Tenant-scoped: Yes (tenant DB - requires x-client-id)

Request Headers

Header	Value	Description
Authorization	Bearer <chat_user_token>	Chat user Bearer token for a participant allowed to edit group info (admin when `onlyAdminCanEditInfo` is true).
is-tenant	true	Targets the tenant DB ("true", needs x-client-id).
x-client-id	{{clientId}}	Tenant (client) id. Required when is-tenant=true.
Content-Type	application/json	JSON request body.

Request Payload

Example updating group name, description, avatar URL, and metadata:

json

1{2  "conversationId": "694b...d8",3  "groupName": "Dev Team 2.0",4  "groupDescription": "Now with more sprints",5  "groupImage": "https://cdn.example.com/group-v2.png",6  "metadata": {7    "workspaceId": "c1"8  }9}

Success Response (HTTP 200 OK)

On success, data.conversation contains the updated group document. Refresh the SDK header, avatar, and info panel from these fields.

json

1{2  "success": true,3  "message": "Group information updated successfully",4  "data": {5    "conversation": {6      "_id": "694b...d8",7      "conversationType": "group",8      "groupName": "Dev Team",9      "groupDescription": "Sprint coordination",10      "groupImage": null,11      "participants": [12        "694b...a1",13        "694b...a2",14        "694b...a3"15      ],16      "groupAdmins": [17        "694b...a3"18      ],19      "owner": "694b...a3",20      "groupPermissions": {21        "onlyAdminCanSendMessage": false,22        "onlyAdminCanEditInfo": false,23        "senderCanEditMessage": true,24        "allowMemberAdd": true,25        "allowMemberRemove": false,26        "moderationEnabled": false27      },28      "unreadCount": {},29      "pinnedMessage": [],30      "lastMessage": "70a1...c4",31      "metadata": {32        "workspaceId": "c1"33      },34      "createdAt": "2026-07-10T09:00:00.000Z",35      "updatedAt": "2026-07-10T09:00:00.000Z"36    }37  },38  "error": null39}

Common Errors

Information updates fail when the token is invalid, the conversation is missing, the caller cannot edit info, or no updatable fields were sent.

HTTP 401 Unauthorized - No token

json

1{2  "success": false,3  "message": "No token, authorization denied",4  "data": null,5  "error": "Unauthorized"6}

HTTP 403 Forbidden - Insufficient permissions

json

1{2  "success": false,3  "message": "Access denied: insufficient permissions",4  "data": null,5  "error": null6}

HTTP 404 Not Found - Conversation missing

json

1{2  "success": false,3  "message": "Conversation not found",4  "data": null,5  "error": null6}

HTTP 400 Bad Request - No fields to update

json

1{2  "success": false,3  "message": "At least one field to update is required",4  "data": null,5  "error": null6}

Code	Reason
401 Unauthorized	Chat user token is missing, invalid, or expired.
403 Forbidden	Caller cannot edit group info (non-admin when `onlyAdminCanEditInfo` is true).
404 Not Found	No group conversation matches `conversationId`.
400 Bad Request	Empty body or no updatable fields besides `conversationId`.
500 Internal Server Error	An unexpected error occurred while updating group information.

Best Practices

Upload avatars to your own storage and pass a stable HTTPS URL in groupImage - do not send raw binary in this endpoint.
Send only changed fields to avoid accidental overwrites of description or metadata.
Check groupPermissions.onlyAdminCanEditInfo before showing edit controls to regular members.
Optimistically update the SDK UI, then reconcile with the response on success or roll back on error.

Group info updated

Refresh the conversation list title, header avatar, and group info screen from data.conversation. Use Group Permissions for behavior flags - this endpoint only updates display metadata.

Overview

Only the fields you send are updated; omit fields you want to leave unchanged. The response returns the full updated conversation document.

When to use this endpoint?

Use Update Group Information when:

A user renames the group from the SDK header or info panel.
You update the group description or avatar after branding changes.
You sync metadata from an external workspace (project id, channel slug, and so on).
You save changes from a group edit form after loading conversation details.

Request Fields

Field	Type	Required	Description
conversationId	string	Required	The group conversation's `_id`.
groupName	string	Optional	New display name for the group in the SDK conversation list and header.
groupDescription	string	Optional	Updated description shown in group info screens.
groupImage	string	Optional	URL for the group avatar. Upload the image to your CDN or storage first, then pass the public URL here.
metadata	object	Optional	Arbitrary key-value map merged or replaced per your API behavior - use for app-specific group attributes.

Request Headers

Header	Value	Description
Authorization	Bearer <chat_user_token>	Chat user Bearer token for a participant allowed to edit group info (admin when `onlyAdminCanEditInfo` is true).
is-tenant	true	Targets the tenant DB ("true", needs x-client-id).
x-client-id	{{clientId}}	Tenant (client) id. Required when is-tenant=true.
Content-Type	application/json	JSON request body.

1{2 "conversationId": "694b...d8",3 "groupName": "Dev Team 2.0",4 "groupDescription": "Now with more sprints",5 "groupImage": "https://cdn.example.com/group-v2.png",6 "metadata": {7 "workspaceId": "c1"8 }9}

Success Response (HTTP 200 OK)

On success, data.conversation contains the updated group document. Refresh the SDK header, avatar, and info panel from these fields.

json

1{2  "success": true,3  "message": "Group information updated successfully",4  "data": {5    "conversation": {6      "_id": "694b...d8",7      "conversationType": "group",8      "groupName": "Dev Team",9      "groupDescription": "Sprint coordination",10      "groupImage": null,11      "participants": [12        "694b...a1",13        "694b...a2",14        "694b...a3"15      ],16      "groupAdmins": [17        "694b...a3"18      ],19      "owner": "694b...a3",20      "groupPermissions": {21        "onlyAdminCanSendMessage": false,22        "onlyAdminCanEditInfo": false,23        "senderCanEditMessage": true,24        "allowMemberAdd": true,25        "allowMemberRemove": false,26        "moderationEnabled": false27      },28      "unreadCount": {},29      "pinnedMessage": [],30      "lastMessage": "70a1...c4",31      "metadata": {32        "workspaceId": "c1"33      },34      "createdAt": "2026-07-10T09:00:00.000Z",35      "updatedAt": "2026-07-10T09:00:00.000Z"36    }37  },38  "error": null39}

Common Errors

Information updates fail when the token is invalid, the conversation is missing, the caller cannot edit info, or no updatable fields were sent.

HTTP 401 Unauthorized - No token

json

1{2  "success": false,3  "message": "No token, authorization denied",4  "data": null,5  "error": "Unauthorized"6}

HTTP 403 Forbidden - Insufficient permissions

json

1{2  "success": false,3  "message": "Access denied: insufficient permissions",4  "data": null,5  "error": null6}

HTTP 404 Not Found - Conversation missing

json

1{2  "success": false,3  "message": "Conversation not found",4  "data": null,5  "error": null6}

HTTP 400 Bad Request - No fields to update

json

1{2  "success": false,3  "message": "At least one field to update is required",4  "data": null,5  "error": null6}

Code	Reason
401 Unauthorized	Chat user token is missing, invalid, or expired.
403 Forbidden	Caller cannot edit group info (non-admin when `onlyAdminCanEditInfo` is true).
404 Not Found	No group conversation matches `conversationId`.
400 Bad Request	Empty body or no updatable fields besides `conversationId`.
500 Internal Server Error	An unexpected error occurred while updating group information.

Best Practices

Upload avatars to your own storage and pass a stable HTTPS URL in groupImage - do not send raw binary in this endpoint.
Send only changed fields to avoid accidental overwrites of description or metadata.
Check groupPermissions.onlyAdminCanEditInfo before showing edit controls to regular members.
Optimistically update the SDK UI, then reconcile with the response on success or roll back on error.