--- title: "POST - Host Remediation" slug: "post-host-remediation" tags: ["EDR with Forensics (EDRF)", "Endpoint Security"] updated: 2026-08-26T19:31:02Z published: 2026-08-26T19:31:02Z canonical: "docs.trellix.com/post-host-remediation" --- > ## 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. # POST - Host Remediation ### Overview This endpoint executes a specific command, like quarantining or killing a process, on one or more endpoints. Provide the action, target `hostIds`, and any required `actionInputs`. The API creates an asynchronous job and returns an ID for tracking the outcome. Use this API for urgent, manual interventions, like an analyst quarantining a compromised endpoint, or for playbooks that perform specific system tasks outside of a formal threat response. This API provides granular, command-level control, offering a flexible response capability that is not limited to pre-defined threat detections. ### 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)* ``` POST https://{Trellix EDR_gateway_URL}/edr/v2/remediation/host ``` You can get the gateway URL from the Trellix on-boarding email. For example, `https://api.manage.trellix.com`. ### Request ###### Request headers ``` Authorization: Bearer Content-Type: application/vnd.api+json x-api-key: X-MVEDR-Source: X-Trace-Id: ``` - **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. - **X-MVEDR-Source** (Optional): Indicates the region or source of the event data using the format `xdrsoar:<region>`. For example, `xdrsoar:us-west`. - **X-Trace-Id** (Optional): Supports tracking headers trace using the format `workflow-id:task/step-id`. For example, `execution-id:task/step-id`. ###### Request body **Example 1:** ``` {  "data": {    "type": "hostRemediation",    "attributes": {      "action": "quarantineHost",      "hostIds": [        "C6C4B1D2-1EDD-11ED-178D-005056AC6A75",        "C6C4B1D2-1EDD-11ED-178D-005056AC6A76"      ]    }  } } ``` **Example 2:** ``` {  "data": {    "type": "hostRemediation",    "attributes": {      "action": "killProcessByName",      "hostIds": [        "E4F47D88-BB73-11EF-0ABE-005056A48646"      ],      "actionInputs": [        {          "name": "name",          "value": "explorer.exe"        }      ]    }  } } ``` > [!NOTE] > Note > > *Name* and *value* pair combination is unique for the provided action. Any incorrect combination results in the API showing an error. **Example 3:** ``` {  "data": {    "type": "hostRemediation",    "attributes": {      "action": "_create_file_win",      "actionInputs": [        {          "name": "full_path",          "value": "C:/Users/cdaauto/AppData/Local/Temp/MVAPITest_HR.txt"        }      ],      "hostIds": [        "51C07FCA-08AD-11F1-04E0-005056AC90E3"      ]    }  } } ``` > [!NOTE] > Note > > Custom reactions are prefixed with `_`. ###### Request parameters There are no request parameters. ### Response ###### Response example ``` {  "data": {    "type": "hostRemediation",    "id": "hr-5432",    "attributes": {      "success": [        {          "status": "200",          "message": "in-progress",          "hostIds": [            "902F4237-B838-ED11-87C6-005056A4B536",            "902F4237-B838-ED11-87C6-005056A4B537"          ]        }      ],      "failed": [        {          "status": "409",          "message": "conflict, Either Some operation is going on Agent guid or its already inQuarantineHoststate",          "hostIds": [            "902F4237-B838-ED11-87C6-005056A4B534",            "902F4237-B838-ED11-87C6-005056A4B535"          ]        }      ]    },    "links": {      "self": "/edr/v2/remediation/queue-jobs/rem-5432"    }  } } ``` ### Response codes | Status | Response | Description | | --- | --- | --- | | 207 | Created | Your request to create a remediation job was accepted and is being processed. The response body will detail which parts of the submission succeeded or failed. | | 400 | Bad request | The server couldn't understand your request, likely due to a syntax error or an invalid parameter. | | 401 | Access denied request | Your request was rejected because it lacks valid authentication credentials. Check your API key and token. | | 403 | Forbidden | You are not authorized to access this resource. While your credentials may be valid, you don't have the necessary permissions. | | 404 | Not Found | The specific resource or endpoint you requested does not exist. | | 415 | Unsupported Media Type | The server rejected your request because the data format `(Content-Type)` is not supported. | | 429 | Too Many Requests | You've exceeded the rate limit by sending too many requests in a short period. The `Retry-After` header in the response will tell you how long to wait before trying again. | | 500 | Internal Server Error | Something went wrong on the server's end. This is not an issue with your request. |