Update a case template
- Base URL
-
https://{kibana_url}
- PUT /api/cases/templates/{template_id}
Fully replaces a case template. Every accepted update creates a new template version; previous versions stay retrievable with the version query parameter of the get template API, and cases keep the version they were created with. You must have the "Manage templates" sub-privilege for the Cases feature of the owning solution. Set dry_run=true to run the full validation without writing. Requires the Cases feature to be enabled in the space.
Request body
-
definitionstring · max length: 30000required -
The template definition as a YAML string: case defaults (name, severity, category, tags, assignees, connector, settings) and a
fieldsarray of inline field definitions or$refentries pointing into the owner's field library. Stored field values appear on cases underextended_fieldskeys shaped<field_name>_as_<storage_type>. -
namestring · min length: 1 · max length: 50 -
The template identity name, unique per owner (case-insensitive). May be omitted when the YAML definition provides a case-default title (
name:), which is then used as the identity name. -
ownerrequired -
The application that owns the cases: Stack Management, Observability, or Elastic Security.
-
Values:
casesobservabilitysecuritySolution -
The words and phrases that help categorize templates. It can be an empty array.
Responses
Indicates a successful call. Returns the new template version, or {"valid": true} for a dry run.
The request body, YAML definition, or template name is invalid, or a resource limit was exceeded (max 200 fields per template).
Authorization information is missing or invalid.
The user does not have the manage templates privilege for the owner.