--- title: "Patch Reaction" slug: "patch-reaction-1" tags: ["Product Usage", "EDR", "Endpoint Security"] updated: 2026-09-03T18:14:35Z published: 2026-09-03T18:14:35Z canonical: "docs.trellix.com/patch-reaction-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Patch Reaction ### Overview This endpoint updates an existing reaction. Provide a JSON payload with the required changes, such as script content, arguments, or execution settings. Use this endpoint to modify and maintain reaction behavior without recreating it. ### Authentication Authentication type: Bearer Token, API Key. You can create a token using client credentials obtained through the [developer portal](https://developer.manage.trellix.com/). The API Key (`x-api-key`) is provided in your onboarding email or on the API Access Management page. ### Path *(or URL)* ``` PATCH https://{Trellix EDR_gateway_URL}/edr/v2/reactions/{reaction-id} ``` ### Request ###### Request headers ``` Authorization: Bearer Content-Type: application/vnd.api+json x-api-key: ``` - **Authorization**: This header is used to authenticate your request. You need to replace `<your_bearer_token>` with the actual token you generate. - **Content-Type**: This header tells the server that the request body format is `json:api`. Even though this specific call has no request body, the API requires this header. - **x-api-key**: This is a custom header required by the Trellix API for authentication. You'll need to replace `<your_api_key>` with the key from your onboarding email or the [API Access Management](https://developer.manage.trellix.com/public) page. ###### Request example ``` {  "data": {    "type": "reactions",    "attributes": {      "name": "Check_New_reaction",      "description": "Updating a new reaction",      "contents": [        {          "platform": {            "name": "windows"          },          "capability": {            "name": "Execute Powershell Script"          },          "content": ""        },        {          "platform": {            "name": "windows"          },          "capability": {            "name": "Execute Powershell Script"          },          "content": "ls"        },        {          "platform": {            "name": "windows"          },          "capability": {            "name": "Execute Powershell Script"          },          "content": "ls"        }      ],      "arguments": [        {          "name": "ABC",          "type": "NUMBER"        }      ],      "timeout": 60    }  } } ``` ### Response codes | Status | Response | Description | | --- | --- | --- | | 204 | OK | Your request was processed successfully. The server has returned the requested data. | | 400 | Bad request | The server couldn't understand your request, likely due to a syntax error or an invalid parameter. |