Case templates: Update
Description
Update a case template. Updates are partial: options you do not send keep their existing values, and options you do send replace their existing values wholesale.
See the Get Cases API to learn more about cases.
Request
HTTP Method: PUT
| Parameter | Description |
|---|---|
| id | The case template ID. |
| name | Optional The updated case template name. |
| emoji | Optional The updated emoji associated with the case template, as a shortcode such as :mag:. |
| options | Optional The case template configuration. See Options fields on the Create case template API. |
Formulas are stored as written and evaluated when a case is created from the template, against the event that triggered the case creation. Editing a formula therefore only affects cases created after the update - cases already created from the template keep the values they were given at creation time.
Sample request
curl -X PUT \
https://<tenant-domain>/api/v1/case_templates/<<case_template_id>> \
-H 'content-type: application/json' \
-H 'Authorization: Bearer <<CREDENTIAL.tines_api_key>>' \
-d '{
"name": "Phishing investigation",
"options": {
"priority": "critical",
"tag_names": ["phishing", "escalated"]
}
}'
Response
A successful request will return a JSON object representing the updated case template.
Field description
| Parameter | Description |
|---|---|
| id | The case template ID. |
| name | The case template name. |
| emoji | The emoji associated with the case template. |
| team | The team the case template belongs to - ID and name. |
| created_at | ISO 8601 timestamp representing the date and time the case template was created. |
| updated_at | ISO 8601 timestamp representing the date and time the case template was updated. |
Sample response
{
"id": 12,
"name": "Phishing investigation",
"emoji": ":fishing_pole_and_fish:",
"team": {
"id": 2,
"name": "Security"
},
"created_at": "2026-05-25T10:00:00Z",
"updated_at": "2026-05-26T09:30:00Z"
}