Expand description
Cases and their comments. Updates use optimistic concurrency through case versions.
Create a NewCase, then build CasePatch values with the IDs and versions
from the latest read. The owner identifies the Kibana solution handling the
case; comments must use the same owner. NewCase::security and
SECURITY_OWNER select the Security solution.
Structs§
- AddComment
POST /api/cases/{caseId}/comments- Case
- A case returned by Kibana. Use its ID and current version to build a
CasePatch. - Case
Comment - A comment body for
Cases::add_comment. - Case
Page - Case
Patch - Changes to one case. Only the fields set here are sent. Unset fields retain their server values; an empty tag list removes all tags.
- Cases
- Comment
Page - Create
Case POST /api/cases- Delete
Cases DELETE /api/cases- Find
Cases GET /api/cases/_find- Find
Comments GET /api/cases/{caseId}/comments/_find- GetCase
GET /api/cases/{caseId}- NewCase
- A case definition for
Cases::create. Cases have no external connector and do not sync alert status unless configured. - Update
Cases PATCH /api/cases
Enums§
Constants§
- SECURITY_
OWNER - The case owner used by the Security solution.