Overview

Watch SMS delivery with Callgoose SQIBS. Sinch posts a delivery report to your SQIBS API endpoint for each recipient. SQIBS opens an incident when a message fails to deliver, so a broken notification or OTP flow is caught early.

You need
A Sinch SMS service plan, and a SQIBS API token
Setup time
About 10 minutes
Result
Failed SMS deliveries open SQIBS incidents

How it works

Sinch
Alert fires
A message fails to reach a recipient.
Sinch
Sends a webhook
A delivery report callback, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Status Failed opens it.

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. Add a filter with these values (there is no built-in Sinch template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "status" Failed Opens an incident.
Title from "status" Becomes the incident title.
Description from "recipient" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

Delivered reports match no filter and are ignored. Key value contains needs all its values in the message, so add one filter each for Expired and Rejected if you also want those. Sinch does not send a recovery, so close these incidents in SQIBS when the cause is fixed.

Not sure of a key? Send one test message first (step below), then build the filter from the real payload.

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: Send delivery reports to SQIBS

  1. Use your SQIBS endpoint as the callback URL:
https://<your-endpoint>/sqibs-api/v1/process?from=sinch&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. Set it as the default callback URL of your service plan in the Sinch Customer Dashboard (SMS > APIs), or pass it as callback_url when you send a batch.
  2. Ask for per-recipient reports: send batches with "delivery_report": "per_recipient".

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 test SMS to a number that cannot receive it.
  2. In SQIBS, a new incident opens. A per-recipient delivery report looks like this (shortened):
{
  "type": "recipient_delivery_report_sms",
  "batch_id": "01FC66621XXXXX119Z8PMV1QPQ",
  "recipient": "+15551230000",
  "code": 402,
  "status": "Failed",
  "at": "2026-11-22T10:00:00.000Z"
}

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 callback URL.

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 SMS deliveries start failing, SQIBS can run a workflow that switches OTP delivery to a backup sender and posts the result to the incident.

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: