---
title: "Rename a workspace team"
method: PATCH
path: "/workspaces/{workspaceId}/teams/{teamId}"
tags: ["Teams"]
---

# Rename a workspace team

`PATCH /workspaces/{workspaceId}/teams/{teamId}`

## Request

- Base URL: `https://app.communicate.so/api/v1`
- URL: `https://app.communicate.so/api/v1/workspaces/{workspaceId}/teams/{teamId}`
- Auth: one of:
  - HTTP bearer
  - API key in cookie `__Secure-better-auth.session_token`
  - API key in cookie `better-auth.session_token`

Use an explicitly scoped user-bound account bearer credential or an application session. Scope grants are intersected with live membership, role, tenant isolation, agent access and plan limits; a credential does not grant an owner role. Invitation acceptance requires the verified recipient email.

## Path parameters

- `workspaceId` string, required
- `teamId` string, required

## Request body

- UpdateTeamRequest
  - `name` string, required

## Response `200`

Rename a workspace team

- UpdateTeamResponse
  - `id` string, required
  - `workspaceId` string, required
  - `name` string, required
  - `createdAt` string, date-time, required

## Other responses

- `400`: Invalid request, timezone, resource association or confirmation.
- `401`: Missing, invalid, expired or revoked account credential or application session.
- `402`: Plan entitlement or seat capacity does not allow the operation.
- `403`: Required account scope, live verified identity, membership or role permission is missing.
- `404`: Workspace or addressed resource is not visible to this member.
- `500`: Unexpected server failure.
- `503`: Authorization service temporarily unavailable.

---

[API](https://skmtc.dev/communicate/apis/communicate-public-rest-api-2.md) · [All operations](https://skmtc.dev/communicate/apis/communicate-public-rest-api-2/llms.txt) · [OpenAPI document](https://skmtc.dev/communicate/apis/communicate-public-rest-api-2/revisions/db6be3d36733?raw)