[Security Solution] Create missing OpenAPI specs for Endpoint exceptions API

[maximpn]

Epic: https://github.com/elastic/security-team/issues/9531

Deadline: Jul 29, 2024 (see milestones in https://github.com/elastic/security-team/issues/9400)

Summary

As part of the Serverless project, we need to create OpenAPI specs for all public Endpoint exceptions API endpoints, because we want all of them documented before Serverless GA. Please look for more context in the epic.

During a Security Solution public API research we discovered that some public Endpoint exceptions API endpoints have missing OpenAPI specs. We need to add them.

API endpoints

The following public API endpoints were discovered during research, and don't have any OpenAPI specs:

• [ ] POST /api/endpoint_list
• [ ] POST /api/endpoint_list/items
• [ ] GET /api/endpoint_list/items
• [ ] PUT /api/endpoint_list/items
• [ ] DELETE /api/endpoint_list/items
• [ ] GET /api/endpoint_list/items/_find

To do

• Create OpenAPI specs for the endpoints listed above.
• Check if there are any other public endpoints that you own that don't have OpenAPI specs and add them to the list above.
• Make sure the specs you add are valid OpenAPI documents.
• Make sure the specs you add match the actual API contract defined in the code.
• Mark the endpoints as available in ESS, or Serverless, or in both offerings (depends on: https://github.com/elastic/security-team/issues/9516).

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[elasticmachine]

Pinging @elastic/security-detection-engine (Team:Detection Engine)

[elasticmachine]

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)