Extend Liongard API to allow modifying of entity data (Alerts/Tickets)
under review
R
Ryan Rosenkaimer
I'd like to see the API for alerts and other entities be extended to allow modifications (POST or PATCH) back to the alerts themselves. Reasoning for this is to allow callbacks from other systems and/or ticketing systems where our techs are working said alerts and need them to be updated to prevent duplicate work on their part. This is to open support for other outside applications then just what Liongard has integration support for today. Example:Since Liongard doesn't have ticket write back from Autotask due to limitations from Autotask's platform, we could force an API trigger from Autotask's REST API and then parse the response through a automation system (like N8N or Zappier) to prepare the JSON response and write it back to Liongard to modify the alert/ticket details.
E
Ed Million
This is MUCH needed. For partners like us who have staff dedicated to developing with vendor integrations, this level of API functionality is what sets vendors apart for us.The inability to update triggered alerts via the API (when combined with lack of granularity in permissions around interacting with alerts without having admin rights) keeps us from utilizing many of the alerts from Liongard that we would find useful.