Actions86
- RemoteAccess Actions
- Reseller Actions
- List Reseller Invoices
- Get Reseller Invoice
- List Account Usage Line Items
- List Organization Usage Line Items
- List Reseller Subscriptions
- Get Reseller Subscription
- Update Reseller Subscription
- Upgrade Reseller Subscription
- List Accounts
- Create Account
- Get Specific Account
- Update Account
- Get Agent
- Update Agent
- Uninstall Agent
- Isolate Agent
- Release Agent Isolation
- List External Ports
- Get External Port
- List Account Invoices
- Get Account Invoice
- List Incident Reports
- Get Incident Report
- List Memberships
- Create a Membership
- Get Membership
- Update a User's membership
- Delete Membership
- List Organizations
- Create an Organization
- Get Organization
- Update an Organization
- Delete an Organization
- List Remediations
- Get Remediation
- Bulk Approve Remediations
- Bulk Reject Remediations
- List Summary Reports
- List Signals
- Get Signal
- List Remote Access Connections
- Get Actor
- SIEM Actions
- Accounts Actions
- Actor Actions
- Agents Actions
- Invoices Actions
- Escalations Actions
- ExternalRecon Actions
- Identities Actions
- IncidentReports Actions
- Users Actions
- Organizations Actions
- PlatformActions Actions
- SummaryReports Actions
- Signals Actions
- UnwantedAccessRules Actions
- KnownVPNs Actions
IncidentReports → Bulk Reject Remediations
AI-generatedSummary
Rejects remediations in bulk for a specified Huntress incident report, sending a required explanation and a boolean indicating whether the remediation plan was useful. Optional contact details identify who is rejecting the plan and how Huntress SOC can reach them.
Inputs
- Incident Report Id (required) — The incident report ID whose remediations will be rejected.
- Comment (required) — Why the remediations were rejected; this helps Huntress SOC analysts revise the remediation plan and re-issue the incident report.
- Useful (required) — Whether the remediation plan was useful.
- Additional Fields — Optional rejecting user's name, phone number, and email. If omitted, each falls back to the corresponding information for the user attached to the API key.
- Options — Optional custom JSON body, HTTP headers, query filters, batching, debug output, pagination settings, and request timeout.
Output shape
An API response for the bulk rejection request.
The supplied source pack contains only function and class signatures, not implementation bodies, so the precise response shape and whether optional request settings are used by this operation cannot be confirmed.
Examples
Example 1: Reject remediations for an incident report
Provide the incident report ID, a comment explaining the rejection, and whether the plan was useful. Optionally provide contact details for the rejecting user.