A Notify delivery callback is a URL that sends webhooks that provide you with information about how many messages were sent and if those messages were sent correctly by the Notify API. Let's keep in mind that Notify is a bulk-first messaging API, where one API call can trigger from zero to multiple thousands of messages.
Note: Each Callback will contain the status for up to 1000 SMS and/or pushes.
Every callback contains a list of the deliveries-messages that were sent as part of the notification.
The status of one notification can be delivered in one or multiple delivery callbacks, depending on the size of the notification. The final callback from the Notify API will always have a flag IsFinal set to True to indicate that notification is handled completely.
Every delivery in the list has one of the following status:
Notify callbacks do not update the state of the message once it has been passed to the channel. It means there will be no further updates when a recipient has received a message.
Notify delivery callback provides the following payload information.
| Parameter | Type | Description |
|---|---|---|
| NotificationSid | string | A 34 character string that uniquely identifies the Notification that triggered the Delivery attempt |
| AccountSid | string | The unique ID of the Account that sent this notification |
| ServiceSid | string | The unique ID of the Service that sent this notification |
| Count | integer | Number of Deliveries in this report |
| SequenceId | integer | Sequence number of the batch starting from 0 |
| IsFinal | boolean | Flag to indicate it is the final batch for the bulk notification |
| DeliveryState | JSON | The status of this Delivery attempt |
The DeliveryState indicates the status of a delivery attempt. The number of performed delivery attempts should be equal to the number of DeliveryState parameters shown in the payload.
| Parameter | Type | Description |
|---|---|---|
| sid | string | Provider unique message id (for APN/FCM) or message sid (SMxxx for SMS, MMxxx for MMS, RUxxx for rest of adapters) |
| type | string | Channel type (e.g., APN, FCM, SMS, etc...) |
| status | string | SENT or FAILED |
| identity | string | Identity |
| error_code | Integer (optional) | Twilio error code, if an error happened. For more information, go to Twilio error codes |
Content-Type: application/x-www-form-urlencoded
_10&SequenceId=0_10&NotificationSid={NotificationSid}_10&IsFinal=False_10&Count=2_10&DeliveryState[0]="{ \"sid\": \"message sid\", \"channel\": \"APN\", \"status\": \"SENT\" }"_10&DeliveryState[1]="{ \"sid\": \"message sid\", _10 \"channel\": \"APN\", _10 \"status\": \"FAILED\",_10 \"error_code\": 52131,_10 \"error_message\": \"The provided APNs device token has been unregistered\" }"
The Notification's resource accepts an optional "DeliveryCallbackUrl" field that should contain a URL that will be called to provide the Notification status, as shown in the following example:
_10curl -X POST 'https://notify.twilio.com/v1/Services/ISXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/Notifications' \_10 --data-urlencode 'Identity=00000001' \_10 --data-urlencode 'Body=Hello Bob' \_10 --data-urlencode 'DeliveryCallbackUrl=https://myhost/notifyCallbacks'_10 -u $TWILIO_ACCOUNT_SID:$TWILIO_AUTH_TOKEN