> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/developers/api-documentation/service/delete-service-status.md).

# Delete service status

Delete a given service status. A status that is the tenant's default start status cannot be deleted, and the request is refused with a conflict until another default is chosen or the setting is cleared. A status that is still referenced cannot be deleted either: while any service order carries it, any timeline event carries it, or any status message rule fires on it, the request is refused with a conflict. Deprecate the status instead — it is then kept for the service orders that already carry it and is no longer offered when picking a status, which is what retiring a status from the workflow means. Configuring the workflow is separated from working on the service orders that run through it: this is a configuration write and asks for SERVICE\_CONFIG, while reading statuses asks for any service permission.

Required permissions: SERVICE\_CONFIG

```json
{"openapi":"3.0.2","info":{"title":"Flow Retail API version 2","version":"2.0.0"},"tags":[{"name":"Service","description":"Service"}],"servers":[{"description":"Flow Retail Production","url":"https://api.flowretail.com/v2"},{"description":"Flow Retail Stage","url":"https://api.stage.flowretail.com/v2"}],"security":[{"accessToken":[]},{"authToken":[]},{"integrationToken":[]}],"components":{"securitySchemes":{"accessToken":{"description":"Access token recevied after user login with a deviceToken","scheme":"bearer","type":"http"},"authToken":{"description":"Token received from the auth service","scheme":"bearer","type":"http"},"integrationToken":{"scheme":"bearer","type":"http"}}},"paths":{"/tenants/{tenantUid}/serviceorders/statuses/{serviceStatusUid}":{"delete":{"summary":"Delete service status","operationId":"delete-serviceorders-statuses","description":"Delete a given service status.\nA status that is the tenant's default start status cannot be deleted, and the request is refused with a conflict until another default is chosen or the setting is cleared.\nA status that is still referenced cannot be deleted either: while any service order carries it, any timeline event carries it, or any status message rule fires on it, the request is refused with a conflict. Deprecate the status instead — it is then kept for the service orders that already carry it and is no longer offered when picking a status, which is what retiring a status from the workflow means.\nConfiguring the workflow is separated from working on the service orders that run through it: this is a configuration write and asks for SERVICE_CONFIG, while reading statuses asks for any service permission.\n\nRequired permissions: SERVICE_CONFIG","responses":{"204":{"description":"No Content"},"409":{"description":"Conflict. The status cannot be deleted. Either it is the tenant's default start status, which is resolved by choosing another default or clearing the setting, or it is still referenced by a service order, a timeline event or a status message rule, which is resolved by deprecating the status instead: it is then kept for the records that carry it and is no longer offered when picking a status."}},"tags":["Service"]}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flowretail.com/docs/developers/api-documentation/service/delete-service-status.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.