---
title: "Create status"
method: POST
path: "/api/v1/statuses"
tags: ["statuses"]
---

# Create status

`POST /api/v1/statuses`

Creates a new custom status within the caller account.

## Request body

- StatusCreate
  - `entityType` 'ORDER' | 'FULFILLMENT_ORDER', required
  - `code` string, required
  - `label` string, required
  - `description` string, required
  - `nature` 'INITIAL' | 'PROCESSING' | 'FINAL' | 'ERROR', required
  - `color` string, required

## Response `201`

Status created.

- StatusCreateResponse
  - `id` string, required
  - `entity_type` 'ORDER' | 'FULFILLMENT_ORDER', required
  - `code` string, required
  - `label` string, required
  - `description` string, required
  - `nature` 'INITIAL' | 'PROCESSING' | 'FINAL' | 'ERROR', required
  - `color` string, required
  - `origin` 'KRUZER' | 'CUSTOM', required
  - `active` boolean, required
  - `created_at` string, required
  - `updated_at` string, required

## Other responses

- `400` — Request payload, query string, or path parameter failed validation.
- `401` — Authentication is missing, malformed, expired, or refers to a session that is no longer active.
- `403` — The caller is authenticated but lacks the required permission for this action.
- `409` — A status with the same code already exists for the entity type, as a custom or KRUZER base status.
- `422` — The payload passed schema validation but breaks a domain invariant.
- `500` — Unexpected server error. The response body never leaks internal details.

---

[API](https://skmtc.net/kruzer-corp/apis/oms-api.md) · [All operations](https://skmtc.net/kruzer-corp/apis/oms-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/kruzer-corp/oms-api/revisions/38ef6e16a7a8/schema)