Kevin R McGillicuddy
I am not show how feasible this but API data on an incident through incident_reports can be inconsistent example (summary field can be null) or incredibly hard to parse to anything useful as JSON or markup.. example the body field
https://api.huntress.io/docs#tag/incident-reports/get/v1/incident_reports/{id}
the <Content> right now is a very messy long string with escaped characters that varies greatly depending on the type of incident which makes it almost unusable to present to customers
"body": {
"type": "string",
"description": "Autogenerated content describing the details of the incident in question.",
"examples": [
"<Content>"
]
},