Delivery Receipt (DLR)

Delivery Receipt (DLR), also known as SMS Delivery Status Report. It is a service for developers to programmatically obtain the status of SMS delivery, Unimatrix supports proactive pushing of SMS status reports via Webhook.


This feature is an extension service and is not enabled by default. Please go to Extensions - Delivery Receipt in the Console to configure according to your actual needs.

Set the Webhook URL for receiving status reports and specify the request body data format you need to receive, supporting JSON or XML, default is JSON. That completes the basic configuration and is ready for access.


Unimatrix will send an HTTP request to the Webhook URL you set with the POST method, with the body of the request in JSON format for example.

Request Body

idstringMessage ID9f1c4ebbbfacae8d3733abd22f67981c
tostringRecipient's phone number (E.164)+8618600001234
isostringCountry code (iso2)CN
ccstringCountry code (International call prefix)86
messageCountintegerBilling message count1
pricestringConsumption amount0.040000
currencystringBilling currencyCNY
errorCodestringReturn codeDELIVRD
errorMessagestringReturn messageDelivered
submitDatestringSubmit date (ISO 8601)2022-03-07T05:18:00.252Z
doneDatestringDone date (ISO 8601)2022-03-07T05:18:03.252Z

Example content is as follows:

  "id": "9f1c4ebbbfacae8d3733abd22f67981c",
  "status": "delivered",
  "to": "+8618600001234",
  "iso": "CN",
  "cc": "86",
  "messageCount": 1,
  "price": "0.040000",
  "currency": "CNY",
  "errorCode": "DELIVRD",
  "errorMessage": "Delivered",
  "submitDate": "2022-03-07T05:18:00.252Z",
  "doneDate": "2022-03-07T05:18:03.252Z",


A response with HTTP Status Code 200 is considered a successful status report, and Unimatrix does not perform additional checks on the response load.

Signature verification

To further secure your data, Unimatrix supports configuring signatures to verify that Webhook requests come from Unimatrix and that the data has not been tampered with during transmission. Simply enable "Signature Verification" in the settings page and set the signature key (Secret).

When signature verification is enabled, Unimatrix will carry the Authorization field in the Webhook request header with the value constructed in the format UNI1-HMAC-SHA256 Timestamp={unix_epoch}, Nonce={nonce_str}, Signature={signature}, as shown in the following example:

Authorization: UNI1-HMAC-SHA256 Timestamp=1646634211, Nonce=0702b4ae425b0c2e, Signature=khZU1yxkyedU+va6L1WVgn418ycXs7xz0kxitwjFvl4=

Extract the Timestamp, Nonce fields and convert their field names to lowercase and add them to the request payload, sort them in dictionary order (ASC) according to the parameter Key, connect the Key-Values with = and the parameter pairs with & to form the text string to be signed, example is as follows:


Using the HmacSHA256 algorithm, a signature is generated on the text string to be signed with the set signature key (Secret), and the output is a Base64 string, as shown in the following example:


The Signature value extracted from Authorization is compared with the generated signature, and the verification is successful if it matches.

Mock Testing

For quick integrate by developers, Unimatrix has kindly provided Mock testing functionality. You can send mock-constructed DLR requests directly to the target server via the console.


After the first push status report fails, Unimatrix will still re-push the message to the target URL until the push is successful or the maximum number of pushes is exceeded. The re-push interval is 1 minute, 5 minutes, 10 minutes, 30 minutes, 1 hour.