Consider the Cardholder changes endpoint which essentially provides a list of events that occurred against a cardholder. These sorts of endpoints provide valuable information for third party integrations such as the ability to provide a history of when a customer has accessed a door.
Gallagher cloud does not provide the ability to add webhooks to receive events as they occur (which probably makes sense from a deployment and possibly security perspective).
Built on top of the base API client we should provide the ability to synchronise with the command centre, these would have to be written to a backend to keep a shadow of what is available on the command centre. The ida of this is not to query the command centre when the application is rendering interfaces.
This ticket has to be expanded with the details, possibly requires an RFC.
Consider the Cardholder changes endpoint which essentially provides a list of events that occurred against a cardholder. These sorts of endpoints provide valuable information for third party integrations such as the ability to provide a history of when a customer has accessed a door.
Gallagher cloud does not provide the ability to add
webhooks
to receive events as they occur (which probably makes sense from a deployment and possibly security perspective).Built on top of the base API client we should provide the ability to synchronise with the command centre, these would have to be written to a backend to keep a shadow of what is available on the command centre. The ida of this is not to query the command centre when the application is rendering interfaces.
This ticket has to be expanded with the details, possibly requires an RFC.