List entries

Delete

Soft-deletes a single entry: the row survives in storage but drops out of every read, and there is no endpoint that brings it back. Nothing cascades, so the entry is refused while anything still points at it - tickets, other list entries, automation conditions and actions, and the SLA pause statuses and rule priorities - and the answer names what is still using it and how many of each; references from soft-deleted tickets count, since those stay restorable. On the ticket status and priority lists the workspace default and any status hidden by default are refused as well.

DELETE /api/{tenant:minlength(2)}/v{version:apiVersion}/list_entries/{list_id}/{id:int}

Authorisation: Minimum role: USER

Request arguments

Name	Type	Source
list_id	Int32
id	Int32

Request body example

Response

Status: 200 (OK)
Type: DTO_acknowledgement

Wrapper: DTO_response_wrap

Other statuses: 400 (BadRequest), 401 (Unauthorized), 403 (Forbidden), 404 (NotFound), 429 (TooManyRequests)

Response body example

DTO_acknowledgement

Name	Type	ReadOnly	Description
message	String		Message

Generated Sep 18, 2026 09:32