---
title: "Rename, recolor or recategorize one team status."
method: PATCH
path: "/team-statuses/{id}"
tags: ["teams"]
---

# Rename, recolor or recategorize one team status.

`PATCH /team-statuses/{id}`

## Request

- Base URL: `https://restivity.ai/api/v1`
- URL: `https://restivity.ai/api/v1/team-statuses/{id}`
- Auth: OAuth 2 (authorization code, authorization URL `https://restivity.ai/oauth/authorize`, token URL `https://restivity.ai/api/oauth/token`, scopes: `projects:write`)

Updates one status by its id. Changing `category` moves every task already in the stage with it, in one step — the answer carries `tasks_moved`, `projects_affected` and `recurring_masters_stopped` (a stage made `completed` completes them). A status of another level is `inherited_palette` (409). MCP sibling: `teams_statuses_update`.

## Path parameters

- `id` string, uuid, required

## Request body

- UpdateProjectStatusInput
  - `name` string
  - `color` string
  - `category` 'todo' | 'in_progress' | 'completed': Which of the base lifecycle states this stage counts as: 'todo' | 'in_progress' | 'completed'. Drives filters, completion stats and the base `status` of every task moved into it.

## Response `200`

The updated status and the side effects of a category change.

- ScopeStatusUpdateResult
  - `status` ProjectStatus, required
    - `id` string, uuid, required
    - `workspace_id` string, uuid, nullable, required: Set when the status belongs to a workspace palette; otherwise null.
    - `team_id` string, uuid, nullable, required: Set when the status belongs to a team palette; otherwise null.
    - `project_id` string, uuid, nullable, required: Set when the status belongs to the project's own palette; null for a workspace or team status.
    - `name` string, required
    - `color` string, required
    - `position` integer, required: Pipeline order, ascending.
    - `category` 'todo' | 'in_progress' | 'completed', required
    - `created_at` string, required
  - `tasks_moved` integer, required: Tasks that changed base `status` with the stage (a category change moves them in one step).
  - `projects_affected` integer, required: Projects those tasks are in.
  - `recurring_masters_stopped` integer, required: Recurring reminder masters whose series this category change stopped (a stage made `completed` completes them, T046a/AGF-59).

## Other responses

- `400`: Invalid request shape.
- `401`: Missing or invalid access token.
- `403`: Token lacks the required scope.
- `404`: No such workspace / team / status visible to the caller — a malformed (non-UUID) id included, like every v1 route.
- `409`: The write conflicts with the palette state: `inherited_palette` (the list follows the one above it, or the status is of another level), `already_own`, `already_following`, `replacement_required` (tasks sit in the status — the problem carries `usage: {tasks, projects}`), `status_limit_reached` (15).
- `422`: Request body failed schema validation.
- `429`: Rate-limit exceeded for this tier.

---

[API](https://skmtc.dev/restivity/apis/restivity-rest-api.md) · [All operations](https://skmtc.dev/restivity/apis/restivity-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/restivity/apis/restivity-rest-api/revisions/5764e41ebb3a?raw)