---
title: "Update team"
method: PUT
path: "/teams/{name}"
---

# Update team

`PUT /teams/{name}`

Update a team with a new name or name. Note that updating the team with a new name will cause all your URLs to change!

## Path parameters

- `name` string, required — The name of the team to update

## Request body

- UpdateTeamParams
  - `$schema` string, uri — A URL to the JSON Schema for this object.
  - `execution_region` 'eu-central-1' | 'us-east-1' | 'us-west-2' | 'eu-west-1' | 'ap-northeast-1' | 'ap-southeast-2' — The execution region for runs
  - `name` string, nullable, required — The name of the team to update. This is optional, if you supply null it will not update the team name.

## Response `200`

OK

- UpdateTeamResponse
  - `$schema` string, uri — A URL to the JSON Schema for this object.
  - `team` Team, required
    - `execution_region` string, required
    - `name` string, required
    - `organization` string, required — The name of the organization this team belongs to.
    - `slug` string — This property is deprecated. Use name instead.
    - `token` Token
      - `access_token` string, required — The access token to use when authenticating API requests with Tower.
      - `jwt` string, required — This property is deprecated. Use access_token instead.
      - `refresh_token` string — The refresh token to use when refreshing an expired access token. For security reasons, refresh tokens should only be transmitted over secure channels and never logged or stored in plaintext. It will only be returned upon initial authentication or when explicitly refreshing the access token.
    - `type` string, required — The type of team, either 'personal' or 'team'.

## Other responses

- `default` — Error

---

[API](https://skmtc.net/tower/apis/tower-api.md) · [All operations](https://skmtc.net/tower/apis/tower-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tower/tower-api/revisions/0e42b0fb26d9/schema)
