How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Huntress Incident Reports API

Operations about Incident Reports

Huntress Incident Reports API is one of 17 APIs that Huntress publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Incident Reports. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 7 operations across 7 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.huntress.io.

7 operations 7 paths 5 schemas 4 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.huntress.io/v1
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Huntress Incident Reports API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basic_auth). By default, every request must be authenticated.

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 4 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Incident Reports 7

Operations about Incident Reports

GET
/v1/incident_reports
List Incident Reports
getV1IncidentReports 10 params → 200403
GET
/v1/incident_reports/{id}
Get Incident Report
getV1IncidentReportsId 1 param → 200403
POST
/v1/incident_reports/{id}/resolution
Create an Incident Report Resolution
postV1IncidentReportsIdResolution 1 param → 201403409422
GET
/v1/incident_reports/{incident_report_id}/remediations
List Remediations
getV1IncidentReportsIncidentReportIdRemediations 7 params → 200403
GET
/v1/incident_reports/{incident_report_id}/remediations/{remediation_id}
Get Remediation
getV1IncidentReportsIncidentReportIdRemediationsRemediationId 2 params → 200403
POST
/v1/incident_reports/{incident_report_id}/remediations/bulk_approval
Bulk Approve Remediations
postV1IncidentReportsIncidentReportIdRemediationsBulkApproval 1 param → 201403409422
POST
/v1/incident_reports/{incident_report_id}/remediations/bulk_rejection
Bulk Reject Remediations
RemediationBulkRejectionParameters 1 param body → 201403409422

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are IncidentReport (17 properties), Remediation (8 properties), RemediationBulkRejectionParameters (5 properties), User (3 properties). Each schema is shown below with its type and property counts.

IncidentReport
object
IncidentReport model
17 properties
Pagination
object
Pagination model
2 properties
User
object
3 properties
Remediation
object
Remediation model
8 properties
RemediationBulkRejectionParameters
object
Bulk Reject Remediations Remediations
5 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

huntress-incident-reports-api-openapi.yml Raw ↑

Other APIs Huntress publishes across the network.

Huntress Accounts API
Huntress Actor API
Huntress Agents API
Huntress Escalations API
Huntress External Recon API
Huntress Identities API
Huntress Invoices API
Huntress Known VPNs API
Huntress Organizations API
Huntress Platform Actions API
Huntress Reseller API
Huntress SIEM API
Where this information came from

This is an independent, third-party profile of Huntress Incident Reports API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.