---
title: "Create a service status"
method: POST
path: "/service_statuses"
tags: ["Service Orders"]
---

# Create a service status

`POST /service_statuses`

Creates a new custom service status for the retailer. The new status is
appended at the end of the display order. Use the PATCH endpoint to
change its position after creation.

**Only available with the Service Orders module enabled.**

🔒 Requires: `services:write` scope

## Request body

- object
  - `name` string, required — Human-readable name for the status.

## Response `201`

Service status created successfully

- ServiceStatusDetails, nullable — Details of a custom service status assigned to a service order.
  - `created_at` string, date-time — The date and time the status was created.
  - `display_name` string — Human-readable name of the status.
  - `display_order` integer, nullable — The order in which this status appears in the UI. Null if not set.
  - `id` string — The unique ID of the status.
  - `retailer_id` string — The retailer this status belongs to.
  - `status_key` string — The underlying key mapping this status to a system status (e.g. NEW, IN_PROGRESS).
  - `system_default` boolean — Whether this is a system-managed default status.
  - `updated_at` string, date-time — The date and time the status was last updated.

## Other responses

- `400` — Bad request — name is missing or blank
- `401` — Unauthorized
- `403` — Forbidden — missing `services:write` scope
- `409` — Conflict — a status with this name already exists

---

[API](https://skmtc.net/lightspeedhq/apis/api-2026-07.md) · [All operations](https://skmtc.net/lightspeedhq/apis/api-2026-07/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lightspeedhq/api-2026-07/revisions/72d4ceb46dbb/schema)