Delete an exception list
Spaces method and path for this operation:
<div><span class="operation-verb delete">delete</span> <span class="operation-path">/s/{space_id}/api/exception_lists</span></div>Refer to Spaces for more information.
Delete an exception list using the id or list_id field.
Before deleting an exception list that is linked to detection rules, remove or unlink the exception list from those rules. Deleting a linked exception list can leave rules referencing an exception list that no longer exists.
Query parameters
Exception list's identifier.
Exception list's identifier. Either id or list_id must be specified.
The exception list's human-readable string identifier.
For endpoint artifacts, use one of the following values:
- endpoint_list: Elastic Endpoint exceptions list
- endpoint_trusted_apps: Trusted applications list
- endpoint_trusted_devices: Trusted devices list
- endpoint_event_filters: Event filters list
- endpoint_host_isolation_exceptions: Host isolation exceptions list
- endpoint_blocklists: Blocklist
Human readable exception list string identifier, e.g. trusted-linux-processes. Either id or list_id must be specified.
Determines whether the exception container is available in all Kibana spaces or just the space in which it is created, where:
- single: Only available in the Kibana space in which it is created.
- agnostic: Available in all Kibana spaces.
For endpoint artifacts, the namespace_type must always be agnostic. Space awareness for endpoint artifacts is enforced based on Elastic Defend policy assignments.
single deletes the list in the current Kibana space; agnostic deletes a global list. Must match the list you are removing when using list_id or id.
Response
Successful response
Example response
{
"description": "This list tracks allowlisted values.",
"id": "9e5fc75a-a3da-46c5-96e3-a2ec59c6bb85",
"list_id": "simple_list",
"name": "My exception list"
}