You can use webhook to get real-time notification updates in your application. SuprSend processes data received from your end-vendors in a standard format, so you don’t have to adapt your system for different vendor data structures.

​
How it works?

SuprSend sends a JSON payload to a specified endpoint (URL) as soon as a notification update is received, e.g. when a message is sent, delivered, seen or replied by user. You can configure which events you want to receive on a particular endpoint, allowing you to filter out unnecessary data and only receive the information relevant to your application. Once the data is received, a POST request is sent to the endpoint you’ve provided. You can then use it to store information or trigger specific actions in your app.

​
Set up your Webhook Endpoint

1

Create an endpoint in your application to receive webhook requests

Create an endpoint in your application specifically to receive webhook requests from SuprSend. The endpoint should be an HTTP or HTTPS URL. Once you have created the endpoint, configure it in SuprSend dashboard to receive notification updates. You can use one endpoint per event type or you can send multiple types of events to the same endpoint
2

Add the endpoint in SuprSend dashboard and start receiving events

  • Navigate to the Developers section on SuprSend dashboard and go to Webhooks. On the webhooks page, click on “Enable Webhook”
  • Once you have enabled webhook, you’ll see a screen like below. Click on “Add Endpoint”
  • This will open endpoint settings form. Add the endpoint URL that you have created in the first step and give it a description for your reference. Select the event type that you want to receive on this endpoint for each channel.
  • Here’s how an example configuration of enabling status updates for email notification looks like:
Form Fields and their descriptions:
FieldObligationDescription
URLmandatoryhttp or https endpoint where you want to receive the webhook requests from SuprSend. Must support POST method and content-type should be application/json
Descriptionoptionaladd the reference of what information will be tracked in the given endpoint
Event typemandatoryWhat all events should be tracked in this endpoint at each channel level. In case of WhatsApp, inbound_message = all requests related to user responses and status = notification status such as sent, delivered, seen etc.
Advanced Configuration -> Rate LimitoptionalNumber of webhook requests that you want to receive per second on the given endpoint. After the limit is reached, requests will get throttled so to keep a consistent rate under the limit.
Advanced Configuration -> Custom HeadersoptionalYou’ll be able to add custom headers after saving the webhook endpoint. Content-type = application/json is set by default. You can use this field to set authentication token in SuprSend request

​
Webhook payload structure

This is an example of the webhook payload structure. The payload contains normalized data from SuprSend as well as the vendor response received. The payload structure will be similar for all channels except for vendor response. Vendor response will contain the exact vendor response received from the vendors and will vary based on the structure of vendor response. 
{
  "channel": "whatsapp",
  "channel_value": "+15555555555",
  "distinct_id": "joe@example.com",
  "event_type": "status",
  "reference": {
    "idempotency_key": "44220630-d9ae-49f2-918e-0b2f6018cecf",
    "supr_execution_id": "01GNEQZ65HRWZP5H0JY0TQA9VG",
    "supr_ngid": "01GNEQZ6F2DE7BF0AFTXWZE7AE",
    "supr_nid": "01GNEQZ6F4JZF1BAK9CDXYD4T4",
    "vendor_ack_id": "320xxxx7xxxxxxxxxK-xxxxHxxxx8xxxxxxxx-xxxxYxxxx1xxxxxxxxxxxxx",
    "workspace_name": "staging",
    "workspace_uid": "lap5XXXXXXXXXXX"
  },
  "suprsend_status": {
    "status": "delivered",
    "timestamp": 1672310923000
  },
  "template": "purchase-made",
  "vendor_name": "gupshup",
  "vendor_response": {
    "gupshup": {
      "event_type": "status",
      "response": [
        {
          "cause": "SUCCESS",
          "channel": "WHATSAPP",
          "destAddr": "15555555555",
          "errorCode": "000",
          "eventTs": 1672310923000,
          "eventType": "DELIVERED",
          "externalId": "320xxxx7xxxxxxxxxK-xxxxHxxxx8xxxxxxxx-xxxxYxxxx1xxxxxxxxxxxxx",
          "extra": "",
          "srcAddr": "TESTSM"
        }
      ]
    }
  },
  "version": "1.0",
  "workflow_name": "Purchase Made"
}