Integrations, Webhooks, APIs

Hi, I noticed that when calling the /v1/organizations endpoint, the "identity_provider_tenant_id" only shows something if it is a Microsoft organization - if it is a Google org that has ITDR set up, it just shows null. Looks like Google info is there within "actual_usage" if you fetch the specific org with /v1/organizations/{org_id} - would be nice if we could get that info with the list endpoint though. Thank you!

Hi, I have identified a slight discrepancy with the Huntress API documentation. In the example response for POST and PUT on /v1/organizations, it shows a flat object, whereas in actuality when you call it, it returns an object with the "organization" key. Shown in documentation: { "id": 123, "name": "Some org" ...etc... } Actual return: { "organization": { "id": 123, ...etc... } }

Currently sites are onboarded using the customers name in Datto RMM, if a customers 'site' is renamed in Datto RMM, new devices are pushed into a copy organisation with the new name in Huntress leading to billing issues and duplicate sites. Can Huntress identify customers by their site ID/GUID in Datto NOT their site name.

There is an on/off slider next to each notification type under the email integration This is not functional and cannot enable/disable the emailing of a notification type

The Escalations API currently does not return the Country Name for Unexpected Country (let alone that is an Unexpected Country type - it just is "Microsoft 365 Login"). This would be ideal so we can build automation to resolve automatically (based on info we have in our HRIS) if we know a user is based in the Country detected in the sign in

Hello, I opened a support ticket on this matter and I was directed to this feedback forum. We have an organization that has subscribed to MDR for 365 and has no intention to subscribe to MDR for Endpoint at this time The billing page states there are 0 agents, and it says there is an error under synced agents despite ConnectWise integration showing a sync taking place for this org. The error reads: Last Sync Failed Active agreement addition not found for company We believe this iconography should be revised and changed to an informational type icon, or a warning. Using the icon of an error leads us to believe that there is something we did not properly configure or that something we configured has broken and needs to be repaired That being said, there is no issue at this time as this is the client's intended setup and the only way to "fix" this "error" is to get an agreement provisioned. While we have no intent to do this, if any other actual error did need to be addressed, it becomes easier for us to overlook it as we become accustomed to errors on this having no value/meaning. A change in the icon to informational would help us differentiate if there is actually a problem to be solved here. thank you for your consideration

Have the option to choose between pro-rating or not. May not be possible to prevent this on the first sync but if not pro-rating then it should add licenses at the end of each cycle, not in the middle or set the date correctly when adding.