WebEngage webhooks let you add an
HTTP callback to the events happening in WebEngage. By configuring a webhook, WebEngage is triggered to call a script on your web-servers whenever a particular event, for which you want to get real-time data, occurs and use it for internal purposes. You can use webhooks to send information to systems such as Salesforce. You can also use webhooks to send information to your backend systems. For example, you might want to credit your customers' accounts with promotion credits once they’ve performed a custom event a certain number of times.
Webhook requests will be posted to a URL configured by you and in the format described below. Webhook request method will always be
POST. There will be additional parameters that will be appended to the
Used to identify webhook
Event for which data is being sent
Your WebEngage account license code
This secret key is to be used to identify the webhook
The Request body will contain event-specific data and will vary based on the registered webhook.
WebEngage will understand
HTTP Status, of the response. Responses with
HTTP Status 200 will be treated as successful posts, everything else will be logged as failed webhook posts.
See the section about error handling and retries below to understand what happens in case of failures.
You will find Webhook Secret Key for your account in the Integrations > Webhooks section of WebEngage dashboard. This secret key is to be used to identify the Webhook
POST requests from WebEngage to your servers. WebEngage appends a parameter named
secret in the
postURL. Value of this parameter is the MD5 Hex of the combination of your WebEngage license code and the Webhook Secret Key separated by
Please feel free to drop in a few lines at [email protected] in case you have any further queries. We're always just an email away!
Updated 2 months ago