---
title: "Update Status"
method: PATCH
path: "/v2/statuses/{statusID}"
tags: ["Routes", "Statuses"]
---

# Update Status

`PATCH /v2/statuses/{statusID}`

Updates an existing custom status. Default statuses (0, 1, 2) cannot be modified.

**IMPORTANT NOTE:** Changes to statuses automatically propogate to all tasks currently assigned that status.

**Path Parameters:**

- `statusID` (number, required) - ID of the status to update
    

**Request Body (at least one field required):**

- `name` (string, optional) - New status name, 1-100 characters, must be unique
    
- `description` (string, optional) - New description, max 65535 characters
    
- `sortOrder` (integer, optional) - New display order, 0-99
    

**Validation:**

- Cannot modify default statuses (IDs 0, 1, 2)
    
- If changing name, must not conflict with existing statuses
    
- Status must exist and belong to the customer

## Request body

- object
  - `name` string
  - `description` string
  - `sortOrder` integer

## Response `200`

The operation completed successfully. The response body is empty.

## Other responses

- `400` — The request was malformed — either invalid JSON syntax or a validation failure (missing required field, wrong type, etc.).
- `401` — No `Authorization` header was provided on the request.
- `403` — The supplied credentials are invalid, the customer account is inactive, or the credentials do not have permission to perform this action.
- `404` — The referenced resource does not exist or is not visible to the authenticated customer.
- `409` — The request conflicts with the current state of the resource (e.g. a uniqueness constraint or a referenced parent that is in the wrong state).
- `429` — The per-minute or per-hour rate limit for this credential and method has been exhausted. Inspect the `X-RateLimit-*` headers to determine when to retry.
- `500` — An unhandled server-side error. The body message is generic (`System unavailable...`) when the underlying cause is a database fault; otherwise it reflects the raised error.

---

[API](https://skmtc.net/limblecmms/apis/limble-api-v2.md) · [All operations](https://skmtc.net/limblecmms/apis/limble-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/limblecmms/limble-api-v2/versions/20801e23f7f2/schema)