> 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-order-event.md).

# Delete service-order event

Deprecated. A timeline is corrected by writing, not by erasing: edit the note through the update endpoint when the wording is wrong, make the event internal when it should not have been in front of the customer, and write a new event when the case has moved on. Deleting an entry leaves a history that no longer says what happened. During the deprecation window the delete is refused with a conflict on any event that carries a status change, because removing a status event corrupts the service order's state — the state the case is in is the state its last status event put it in. This endpoint will be removed after the announced deprecation window; see the deprecation log for the date. This is a write on the case, so it belongs to the store that owns the service order: at any other store it is refused with a 403, where the case can be read but not worked on.

Required permissions: SERVICE\_ORDER

```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}/stores/{storeUid}/serviceorders/{serviceOrderUid}/events/{serviceEventUid}":{"delete":{"summary":"Delete service-order event","operationId":"delete-serviceorders-events","deprecated":true,"description":"Deprecated. A timeline is corrected by writing, not by erasing: edit the note through the update endpoint when the wording is wrong, make the event internal when it should not have been in front of the customer, and write a new event when the case has moved on. Deleting an entry leaves a history that no longer says what happened.\nDuring the deprecation window the delete is refused with a conflict on any event that carries a status change, because removing a status event corrupts the service order's state — the state the case is in is the state its last status event put it in.\nThis endpoint will be removed after the announced deprecation window; see the deprecation log for the date.\nThis is a write on the case, so it belongs to the store that owns the service order: at any other store it is refused with a 403, where the case can be read but not worked on.\n\nRequired permissions: SERVICE_ORDER","responses":{"204":{"description":"No Content"},"409":{"description":"Conflict. The event carries a status change: the state a service order is in is the state its last status event put it in, so a status event cannot be deleted."}},"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-order-event.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.