# Any direct API for subscribing to alarms and Acknowledging alarms? **URL:** \ **Category:** Ignition\ **Created:** [September 30, 2022, 2:29pm UTC](https://forum.inductiveautomation.com/t/any-direct-api-for-subscribing-to-alarms-and-acknowledging-alarms/64706 "2022-09-30T14:29:46Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [September 30, 2022, 8:12pm UTC](https://forum.inductiveautomation.com/t/any-direct-api-for-subscribing-to-alarms-and-acknowledging-alarms/64706/4 "2022-09-30T20:12:51Z")
You might take some inspiration from this magical post: > [@New Alarm Alert as a Popup](https://forum.inductiveautomation.com/t/new-alarm-alert-as-a-popup/15828/2): > > I would start this a different route. It looks like you are polling for changes to alarm states, when really, we should be reacting to events relating to alarm state changes. This is going to be a long winded answer, so hear goes. Create a new shared script. For this example, create it at shared.alarming. The following will create an object, that extends Ignition’s AlarmListener interface. This is how we get the alarm event from the gateway to the client. Post the following code: from c… --- _[View the full topic](https://forum.inductiveautomation.com/t/any-direct-api-for-subscribing-to-alarms-and-acknowledging-alarms/64706)._