v53

latestOpenAPI 3.0.3raw.githubusercontent.com2026-08-076771,7565.2 MB
Security Exceptions API

Export an exception 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/exception_lists/_export</span></div>

Refer to Spaces for more information.

Export an exception list and its associated items to an NDJSON file.

post/api/exception_lists/_export

Query parameters

idstring nonempty required

Exception list's identifier.

Example:9e5fc75a-a3da-46c5-96e3-a2ec59c6bb85

Exception list's internal id (UUID) returned on create; use with list_id and namespace_type for an unambiguous target.

list_idstring 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
Example:simple_list

Human-readable list_id of the exception list to export, as shown in the UI and API responses.

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.

single exports a list in the current Kibana space; agnostic exports a global (space-agnostic) list.

include_expired_exceptions'true' | 'false' required

Determines whether to include expired exceptions in the exported list. Expiration date defined by expire_time.

Response

Successful response