📄️ Event Notifications Overview
Push and Pull Notifications (Polling and Webhooks)
📄️ Event Registry
Event Notifications Overview
📄️ Using the Correlation Id Header
When API clients make calls, there is an optional Header that can be passed in the HTTP request. Along with the standard parameters:
📄️ Polling API Walkthrough
Using the APIs to Poll for Notifications
📄️ Webhook API Walkthrough
Using the APIs to Configure Webhook Notifications
📄️ Webhook Security using HMAC
Within our Webhook configuration, there is a field called secret which clients can populate with a string. This string has a cryptographic hash function applied to it using the SHA256 algorithm that in turn produces a hash. The string is not stored by fenergo in plaintext and our service only has access to the hash value. That cryptographic string is combined with the full Body of the webhook message and a signature is calculated (another hash of the encrypted string and the message body). The resulting signature is stored in a header called x-fenx-signature that is included in every webhook message.