Custom Webhooks

Connect has two different objects that you can use to receive information about the Connect and MVS apps while customers are interacting with the web or mobile pages.

webhookData Object

If you pass the webhookData object in the Generate 2.0 Connect URL APIs, you’ll receive the object back in the body for all other Connect and MVS event types.

Example: Pass the webhookData object in a Generate Connect URL call, and you’d receive the started event notification.

Sample webhookData
 "webhookData": {

   "unquiqueCustomerId": "123456789",

   "uniqueRequestId": "234567890"

 }
Sample response
 {

    "customerId":"1005061234",

    "consumerId":"86238nvnw7269e224a4e3de12352d87d",

    "eventType":"started",

    "eventId":"1495468585434-0e73d1719173766fe4dfe1a8",

    "payload":{},

    "webhookData": {

    "unquiqueCustomerId": "123456789",

    "uniqueRequestId": "234567890"

  }

}

webhookHeaders Object

Passing the webhookHeaders object provides similar customer return behavior for every webhook event. However, it returns in the header instead of the body of the event.

Sample webhookHeader 
 "webhookHeaders": {

   "webhookServerKey": "sadf67ewrkh",

   "webhookCustomerSignature": "91l;kj234924987lj"

 }
Sample Generate Connect URL example
 {

  "partnerId": "PARTNER_ID",

  "customerId": "CUSTOMER_ID",

  "type": "aggregation",

  "webhookData": {

    "unquiqueCustomerId": "123456789",

    "uniqueRequestId": "234567890"

  },

  "webhookHeaders": {

    "webhookServerKey": "sadf67ewrkh",

    "webhookCustomerSignature": "91l;kj234924987lj"

  }

}