---
title: "Create an Elastic Endpoint rule exception list"
method: POST
path: "/api/endpoint_list"
tags: ["Security Endpoint Exceptions API"]
---

# Create an Elastic Endpoint rule exception list

`POST /api/endpoint_list`

**Spaces method and path for this operation:**

<div><span class="operation-verb post">post</span>&nbsp;<span class="operation-path">/s/{space_id}/api/endpoint_list</span></div>

Refer to [Spaces](https://www.elastic.co/docs/deploy-manage/manage-spaces) for more information.

Create the exception list for Elastic Endpoint rule exceptions. When you create the exception list, it will have a `list_id` of `endpoint_list`. If the Elastic Endpoint exception list already exists, your request will return an empty response.

## Response `200`

Successful response

- union
  - SecurityEndpointExceptionsAPIExceptionList
    - `_version` string — The version id, normally returned by the API when the item was retrieved. Use it ensure updates are done against the latest version.
    - `created_at` string, date-time, required — Autogenerated date of object creation.
    - `created_by` string, required — Autogenerated value - user that created object.
    - `description` string, required — Describes the exception list.
    - `id` string, nonempty, required — Exception list's identifier.
    - `immutable` boolean, required
    - `list_id` string, nonempty, required — 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
    - `meta` SecurityEndpointExceptionsAPIExceptionListMeta — Placeholder for metadata about the list container.
    - `name` string, required — The name of the exception list.
    - `namespace_type` 'agnostic' | 'single', required — 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.
    - `os_types` SecurityEndpointExceptionsAPIExceptionListOsType[] — Use this field to specify the operating system. Only enter one value.
    - `tags` string[] — String array containing words and phrases to help categorize exception containers.
    - `tie_breaker_id` string, required — Field used in search to ensure all containers are sorted and returned correctly.
    - `type` 'detection' | 'rule_default' | 'endpoint' | 'endpoint_trusted_apps' | 'endpoint_trusted_devices' | 'endpoint_events' | 'endpoint_host_isolation_exceptions' | 'endpoint_blocklists' | 'endpoint_custom_yara_signatures', required — The type of exception list to be created. Different list types may denote where they can be utilized.
    - `updated_at` string, date-time, required — Autogenerated date of last object update.
    - `updated_by` string, required — Autogenerated value - user that last updated object.
    - `version` integer, required — The document version, automatically increasd on updates.
  - object

## Other responses

- `400` — Invalid input data
- `401` — Unsuccessful authentication
- `403` — Insufficient privileges
- `500` — Internal server error

---

[API](https://skmtc.net/elastic/apis/kibana-apis.md) · [All operations](https://skmtc.net/elastic/apis/kibana-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/elastic/kibana-apis/revisions/deb2e8b751e7/schema)