Delivery Report POST
When the network reports the outcome of an SMS, the platform POSTs the status to your URL (notifyUrl) given at send time. Use it to update statuses in your system automatically instead of polling /sms/loginfo.
Setup
Put notifyUrl on each message of POST /sms/send — it is set per message; there is no account-level setting.
{
"messages": [
{
"from": "MYBRAND",
"destinations": [{ "to": "0812345678" }],
"text": "Order #1234 has shipped",
"notifyUrl": "https://example.com/smsup/dr?token=YOUR_SECRET"
}
]
}TIP
Callbacks are sent only for /sms/send messages that have a notifyUrl. /OTP/requestotp accepts a notifyUrl field but sends no callback.
Authorization
Callbacks carry no signature or authentication header — use HTTPS and put your own secret in the notifyUrl (e.g. a token query parameter), then check it on your side.
HTTP Request
POST {notifyUrl}Content Type
application/json (always, regardless of notifyContentType)
Parameter Description
| Property | Type | Description |
|---|---|---|
bulkId | string | bulkId of the /sms/send request that sent this message |
details | array | Results — 1 entry per callback |
details[]
| Property | Type | Description |
|---|---|---|
messageId | string | The network's message reference — may differ from the messageId returned by /sms/send; match on bulkId + to |
mobile | string | Destination number, 66XXXXXXXXX |
to | string | Destination number (same as mobile) |
from | string | Sender name |
text | string | Message text |
credit | number | Credit used for this destination |
sendDate | string | Time sent, yyyy-MM-dd HH:mm:ss (UTC) |
doneDate | string | Time delivered, same format — may be empty "" |
callbackData | string | Reserved — currently always "" |
status | object | Outcome, see below |
status
| Property | Type | Description |
|---|---|---|
code | string | 000 = success, anything else = the network's result code |
name | string | DELIVERED or FAILED |
description | string | Description from the network (may be empty) |
code | name | Meaning |
|---|---|---|
000 | DELIVERED | The network reported success |
| other | FAILED | Not delivered — code and description come from the destination network |
Response Description
Your endpoint must answer HTTP 2xx within 10 seconds — the body can be anything (it is not read).
| Outcome | Platform treats it as |
|---|---|
| HTTP 200–299 within 10 seconds | Delivered, not sent again |
| Any other HTTP status, timeout, connection error | Failed — retried per the table below |
Retry
| Attempt | When |
|---|---|
| 1 | Right after the network result arrives |
| 2 | At least 5 seconds after attempt 1 failed |
| 3 | At least 30 seconds after attempt 2 failed |
After 3 failed attempts the platform stops sending that callback — check the status later with /sms/loginfo.
Request Example
# Simulate a callback to test your endpoint
curl -X POST 'https://example.com/smsup/dr?token=YOUR_SECRET' \
-H 'Content-Type: application/json' \
-d '{
"bulkId": "6f1c2a8e-1b7a-4c35-9d0e-2b8f6f3e9a11",
"details": [{
"messageId": "2611160315200001",
"mobile": "66812345678",
"to": "66812345678",
"from": "MYBRAND",
"text": "Order #1234 has shipped",
"credit": 1,
"sendDate": "2026-11-16 03:15:20",
"doneDate": "",
"callbackData": "",
"status": { "code": "000", "name": "DELIVERED", "description": "" }
}]
}'// Example receiver (Express)
import express from 'express'
const app = express()
app.use(express.json())
app.post('/smsup/dr', async (req, res) => {
if (req.query.token !== process.env.SMSUP_DR_TOKEN) return res.sendStatus(403)
const { bulkId, details = [] } = req.body
for (const d of details) {
// Idempotent update: callbacks for the same message may repeat
await saveStatus({ bulkId, to: d.to, code: d.status.code, name: d.status.name })
}
res.sendStatus(200) // answer fast (within 10 seconds)
})
app.listen(3000)Response Example
HTTP/1.1 200 OKThings to watch
Callbacks can repeat
- Some networks report twice per message (accepted by the network, then delivered to the handset), so you may get more than one callback per number, and both may be
DELIVERED - If your endpoint takes longer than 10 seconds, the platform retries even if you already processed it
Make your endpoint idempotent and treat the latest result as the final status.
TIP
The callback messageId is the network's reference, not the messageId returned at send time. Keep the bulkId and destination number for matching, or send your own bulkId in the /sms/send request.
