# Update Team

`PATCH /people/teams/{id}`

Group: People Management › Teams · Operation ID: `updateTeam`

Updates the team with the given identifier. Only the fields in the request body change, and no field can be cleared. Use the team's id, not its teamNumber.

[Open in the interactive reference](https://docs.api.lensing.ai/?op=updateTeam)

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `Api-Version` | header | `"v1"` | yes | The API version this request targets, named by its public identifier. Required on every request; omitting it, or naming a version this company does not have, is answered with 400. This document describes version `v1`. |
| `Idempotency-Key` | header | string | no | An opaque caller-chosen string (1-255 characters) that makes this request safe to retry. Repeating the same key with an identical request body replays the original response instead of re-executing - but only once that original request succeeded; a failed attempt re-executes on retry. Repeating the key with a different body is answered with 422. A key still in flight is answered with 409 - as is a key whose original request was interrupted before it finished, for a few minutes afterwards, until that attempt is presumed dead. A completed response stays replayable for 24 hours. The key is scoped to the caller, not to the action: reusing it for a different action is answered with 409 or 422 rather than treated independently. On read actions this header is ignored. On write actions that cannot offer the guarantee it is answered with `400 IDEMPOTENCY_NOT_SUPPORTED` rather than silently ignored. |
| `id` | path | string | yes | The unique identifier for the team to update. |

## Request body

Required, `application/json`: updateTeamInput.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no | The name of the team. |
| `teamType` | string, one of `"hrTeam"`, `"psaTeam"` | no | The type of the team. |
| `startDate` | string | no | The first day the team exists. Use format YYYY-MM-DD. |
| `endDate` | string | no | The last day the team exists. Use format YYYY-MM-DD. It may not fall before the team's start date, whether you change that start date in the same request or it is already stored. |
| `parentId` | string | no | The identifier of the team to move this one under. It may not be the team itself or one of its descendants. See id on GET people/teams/:id. |

Example:

```json
{
  "name": "<name>",
  "teamType": "hrTeam",
  "startDate": "<startDate>",
  "endDate": "<endDate>",
  "parentId": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
}
```

## Response

`200` Success

## Response headers

- `Idempotency-Replayed` — Present and `true` only when this response replays a previously stored one for the same Idempotency-Key, rather than reflecting a live execution. Absent on a live response - never sent as `false`.

## Errors

| Code | Status |
| --- | --- |
| `NOT_FOUND` | 400 |
| `PARENT_TEAM_NOT_FOUND` | 400 |
| `PARENT_TEAM_CYCLE` | 400 |
| `INVALID_DATE` | 400 |
| `IDEMPOTENCY_KEY_CONFLICT` | 409 |
| `IDEMPOTENCY_PAYLOAD_MISMATCH` | 422 |

## Statuses

- `400` — Invalid request or business failure. Codes: NOT_FOUND, PARENT_TEAM_NOT_FOUND, PARENT_TEAM_CYCLE, INVALID_DATE
- `401` — Missing or invalid access token
- `403` — Not authorized
- `404` — Not found
- `409` — The Idempotency-Key is still being processed by another request.
- `422` — The Idempotency-Key was already used with a different request payload.
- `429` — Too many requests
- `500` — Internal server error