---
title: "Create Status"
method: POST
path: "/v2/statuses"
tags: ["Routes", "Statuses"]
---

# Create Status

`POST /v2/statuses`

Creates a new custom status for the customer account.

**Request Body:**

- `name` (string, required) - Status name, 1-100 characters, must be unique (case-insensitive)
    
- `description` (string, optional) - Status description, max 65535 characters
    
- `sortOrder` (integer, optional) - Display order, 0-99, auto-assigned if omitted
    

**Response (201 Created):**

- `statusID` (number) - ID of the newly created status
    
- Location header: `/v2/statuses?statuses={statusID}`
    

**Validation:**

- Name must not conflict with existing statuses or defaults ("Open", "In Progress", "Complete")
    
- Name is compared case-insensitively

## Request body

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

## Response `201`

201 Created - Success

- object
  - `statusID` integer

## 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.
- `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/revisions/20801e23f7f2/schema)