Overview

Send Infobip message delivery reports to Callgoose SQIBS, so failed deliveries on your WhatsApp, SMS or other channels become incidents. You create a notification profile that points at your SQIBS API endpoint and subscribe it to delivery events.

You need
An Infobip account with access to Subscriptions management, and a SQIBS API token
Setup time
About 15 minutes
Result
Failed Infobip deliveries open SQIBS incidents

How it works

Infobip
Alert fires
A message delivery report is ready.
Infobip
Sends a webhook
The subscription posts it to the notification profile URL.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
The incident takes its title from the delivery status.

Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.

Step 1: Add the API filter in SQIBS

  1. In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
  2. In Select Integration Template, choose Infobip. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "results".[0]."status"."groupName" (anything) Opens an incident.
Title from "results".[0]."status"."name" Becomes the incident title.
Description from "results".[0]."error"."description" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

The template opens an incident for every delivery report, successful ones included. To open incidents only for failed deliveries, set Key value contains to UNDELIVERABLE (or add filters for REJECTED and EXPIRED), the status groups Infobip uses for failures.

The template is a starting point, not a lock-in: every value stays visible and you can change it.

Find the right key with the JSON key creator
In the API Integration window, click the round {} button at the bottom right. Paste a payload that SQIBS received (copy it from the API log). SQIBS lists every key with its value, each with a copy button. Copy the key into Payload JSON key and the value into Key value contains. No need to read the JSON by hand.

Step 2: Create a notification profile and a subscription

  1. In Infobip, open Developer Tools > Subscriptions management and go to Notification profiles. Create a profile and, in its webhook URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=infobip&token=<your-token>

Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.

  1. Save the profile.
  2. Go to Subscriptions and create a subscription: choose the channel (for example WhatsApp), the delivery events, and the notification profile from step 1. Save it.

For broadcasts, you can also choose to push delivery reports to the webhook in the campaign's Tracking and reporting settings.

Step 3: Test it

The API log saves payloads only while API Tracking is on for the token. Turn it on under API Tokens before you test; it switches itself off after 48 hours.

  1. Send a message to a number that cannot receive it, for example an invalid test number.
  2. In SQIBS, a new incident opens. Infobip's delivery report looks like this (shortened):
{
  "results": [
    {
      "messageId": "139092608552833382",
      "to": "4479000000",
      "channel": "WHATSAPP",
      "status": {
        "groupName": "UNDELIVERABLE",
        "name": "UNDELIVERABLE_NOT_DELIVERED",
        "description": "Message sent not delivered"
      },
      "error": {
        "name": "EC_UNKNOWN_SUBSCRIBER",
        "description": "Unknown subscriber"
      }
    }
  ]
}

No incident? Open the API log (with API Tracking on). If the payload is there, the filter did not match it: paste it into the JSON key creator and check the keys. If it is not there, check the URL and token in the Infobip notification profile.

Fix known issues automatically

Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, when deliveries start failing on a channel, SQIBS can run a workflow that checks your sender registration and switches traffic to a backup sender.

Incident opens
Workflow starts
SQIBS runs the automation workflow linked to the filter.
Fixed
Incident resolved
The issue is fixed before anyone has to step in.
Not fixed
Escalated to the engineer
After the waiting time you set, the escalation policy pages on-call as usual.

Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.

To set it up, in the same API filter:

  1. Select Workflow: choose the automation workflow to run when this filter opens an incident.
  2. If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
  3. Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.

Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.

Learn more: