Genea just got more developer friendly. Now teams can create custom headers and request bodies (payloads) within the code sent from Genea Access Control Webhooks to their web-based applications.
Why are Custom Webhooks Important?
You are likely already familiar with webhooks — messages triggered by an event, such as pushing code to a repository. Webhooks are essentially a mechanism that enables event-driven, one-way information broadcast. They place power in the hands of IT and security professionals, making it possible to integrate disparate systems without touching the source code. But how do custom webhooks benefit IT and security teams when it comes to access control?
How Access Control and Webhooks Work Together
Adjusting headers and bodies within code can help tremendously. For example, if a bank uses a cloud-based access control system and wants to store access events within their proprietary web application, they may decide to use a webhook. The webhook will automatically send information from Access Control to the bank’s application. Once it arrives in the proprietary application, it will be stored accordingly.
Custom Data in Genea Access Control Webhooks
A custom header acts as a flag, informing the proprietary application of the contents within the body of the code. When the event is received, a custom header helps the application decide how the event will be processed. It also helps separate the Access Control information stream from any other webhooks being processed by the same application, as they likely need to be parsed and ingested differently.
Webhook Integrations with Genea
Some common webhook integrations include Datadog, Zapier and IFTTT. However, it is Genea’s goal to give customers unlimited possibilities when connecting web-based applications. We look forward to seeing some exciting integrations from you. For more information, please contact a Genea Access Control expert.