Skip to main content
PATCH/api/public/v1/groups/{id}

groups.update

Rename a group with the revision you last read (groups.list); names are unique, case-insensitive.

Capability: profile.organizeCommand (idempotent)MCP tool: groups_update
View as Markdown

Parameters

NameTypeRequiredDescription
idpathstring (uuid)YesGroup id
command_idbodystring (uuid)YesClient-generated UUID for this command. Send the same id (and body) again to get the stored receipt instead of a second change; a different body under the same id is CONFLICT.
expected_revisionbodyintegerYesThe revision you last read; a newer revision on the server is CONFLICT (min 1, max 9007199254740991)
namebodystringYes(min length 1, max length 60)

Examples

curl -X PATCH "https://browlix.com/api/public/v1/groups/<id>" \
  -H "Authorization: Bearer $BROWLIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"command_id":"<uuid>","expected_revision":1,"name":"<name>"}'

Response

201 with { data, replayed: false, correlation_id } the first time; 200 with replayed: true when the same command_id and body come again.

FieldTypeAlways presentDescription
dataobjectYes
data.group_idstring (uuid)Yes
data.revisionintegerYesThe group's new revision (min -9007199254740991, max 9007199254740991)
correlation_idstring (uuid)Yes
replayedbooleanNotrue when this command_id was already applied and the stored receipt came back

New fields can appear at any time; ignore the ones you do not know.

Errors

CodeHTTPRetryable
UNAUTHENTICATED401No
FORBIDDEN403No
RATE_LIMITED429Yes
VALIDATION_FAILED422No
NOT_FOUND404No
CONFLICT409No
OUTCOME_UNKNOWN202Yes
DEPENDENCY_UNAVAILABLE503Yes
UNKNOWN500No

Every error code and when to retry

All operations