---
title: "Reorder the team's custom statuses."
method: POST
path: "/teams/{id}/statuses/reorder"
tags: ["teams"]
---

# Reorder the team's custom statuses.

`POST /teams/{id}/statuses/reorder`

## Request

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

Sets the left-to-right board order. `ordered_ids` must list EVERY status of the palette exactly once; a partial list is refused (`validation_error`). MCP sibling: `teams_statuses_reorder`.

## Path parameters

- `id` string, uuid, required

## Request body

- ReorderProjectStatusesInput
  - `ordered_ids` string[], required: Every status id of the palette (the list addressed — its `*_statuses_list` gives them), exactly once, in the new left-to-right board order. A partial list is refused (`validation_error`).

## Response `200`

The statuses in their new order.

- ProjectStatusListResult
  - `data` ProjectStatus[], required: The statuses the scope uses, ordered by position (the board order) — its own palette, or the palette of the level it follows (a project: its team or workspace; a team: its workspace; see `inherited_from`). Empty when there are none: the boards that use this palette show the four base lifecycle states.
    - `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
  - `own` boolean, required: true when the scope is on its own palette (a workspace always is) — then its status write operations change it; false when it follows the level above it (a project its team or workspace, a team its workspace).
  - `inherited_from` StatusPaletteSource, required
    - `kind` 'workspace' | 'team', required: The level whose palette the project follows.
    - `id` string, uuid, required: The workspace or team id.
    - `name` string, nullable, required: Its display name; null when the caller cannot see that workspace or team (the id is still given).

## 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)