Integrations, Webhooks, APIs

We are working with Rewst for process automation. It'd be great to be able to uninstall agents via API, create/delete users, isolate machines, etc..

We use a custom browser plugin to pop alert banners when things need attention in Huntress. This works really well for all team members when it comes to incidents but when it comes to escalations there doesn't seem to be any way to review/check for these under the API.

We'd like to automate noting expected user travel (i.e user travelling to Spain for a few days). Requesting an API endpoint to provide user, start date, end date, country would be ideal.

Currently, the API only reports the billable count. It would be very helpful to get the list of agents and users that are being billed for each client. Currently, we are manually generating these reports for clients.

In its current state, expanding the API to include endpoints for MDR for Microsoft 365 would give partners the ability to lookup user principal names, billable status, and if an account has registered MFA.

We would like the ability to create orgs vai API. Use case example - Client approves quote for Huntress and as part of the quote and sales process our systems to make an API call and create the org in Huntress. Ability to set contact for monthly reports and ORG KEY would also be desirable.

Allow the uninstall of Huntress agents via API request. Since tamper protection has been introduced to the Huntress agent, enabling the feature means RMMs can no longer automatically uninstall Huntress from a device. Without an API endpoint to trigger an uninstall, this breaks automation processes and adds new manual tasks that can only be completed in the Huntress portal.

We are not receiving escalations for 'AD Sync Identity Disablement' and 'Login without Entra Usage Location'. This lack of PSA tickets means engineers are unaware of these incidents, as they are not mentioned in the incident ticket. It would be beneficial to have dedicated PSA tickets for these implementations, allowing engineers to see and bundle tickets internally. Alternatively, updating the incident with this information, ideally updating the PSA ticket, would help bring it to the engineers' attention.

Currently in the Autotask Contract Mapping integration - When an Autotask contract needs to be selected for a given customer, all active and inactive contracts are in the list. The list should only contain active contracts. And if a linked contract becomes inactive, it should appear in red, for example, to signal the error more clearly.

We have many Organizations in our Account. For some of those organizations we need to be able to use an API token to integrate with that Organizations SIEM where they have one, or they use a 3rd party that has one. I need a way to create an API key that has RBAC (read only access in this case) and has it to only a single organization.