Hi,
We're writing to let you know about an upcoming enhancement to our messaging delivery receipts (DLRs).
Starting October 15th, we will be introducing two new fields to the DLR payload: sub_error and sub_error_description. Sub_error is a secondary error code that will tie to the sub_error_description and provide a little more detail about why the message was not delivered.
Current fields DLR:
{
"guid": "882e504c-642d-11f1-9a00-403e0194065c",
"account_id": "14990",
"source_did": "19844013003",
"destination_did": "9196146787",
"timestamp": "2026-06-09T18:03:34.000Z",
"send_status": "undeliverable",
"status": "UNDELIV",
"error": "005"
}
Extra fields DLR:
{
"guid": "882e504c-642d-11f1-9a00-403e0194065c",
"account_id": "14990",
"source_did": "19844013003",
"destination_did": "9196146787",
"timestamp": "2026-06-09T18:03:34.000Z",
"send_status": "region-not-supported",
"status": "UNDELIV",
"error": "005",
"sub_error": "3505",
"sub_error_description": "SMS delivery to this region is not available for the operator."
}
No action is required on your part – these fields will simply be added to your existing DLR structure. However, these changes have expanded the data coming back inside of the send_status field, so if you are relying on send_status to be a specific set of values, be aware you will be seeing more statuses when this change is released.
If you'd like early access to these new fields before October 15th, please reach out to our Customer Support team at support@commio.com and we'll be happy to get you set up.
If you have any questions in the meantime, don't hesitate to reach out.
A mapping of DLR error codes is attached.
Comments