» Changes to Delivery Reporting

Message id’s are now also included in your delivery report file, this change is only really relevant for API users, however if  you send messages over 160 characters you will now see multiple entries per message (as there were more than one SMS needed to deliver the message).

The message id is the unique identifier of the message that has been sent. This means that API users can match up the actual message as many messages to the same mobile could have been sent in that day (as you only have one delivery report file per day).

To match the message id you need to use the XML option as described here

Also be aware that if the message required more than one SMS the message id is comma delimited with all the id’s

Popularity: 1%

Related posts:

1. PHP 5 Delivery Report Helper Class for our SMS Gateway
   Class Name: ProcessDeliveryReport This class enables you to access your delivery reports in a nice simplified way. You can search for...
2. Using the SMS Gateway API, Automating Delivery Report Collection
   This blog post has been superseded with our website documentation Introduction If you are using the API / Gateway to send bulk SMS...
3. SMS Gateway API – Specification
   This blog post has been superseded with our website documentation It is recommended that you use the  RESTful version of the API which has largely superseded this document...
4. Concatenated “Long Message” SMS feature now Live for the Bulk SMS system and the SMS Gateway
   You can now send text messages longer than 160 characters, in fact up to 612 characters which arrive as 1...
5. The SMS Gateway
   How to use an SMS Gateway Continue reading →...
6. New Concatenated Bulk SMS Text Message feature due to be released
   A few months ago we conducted customer research asking if a ‘concatenated text message’ or ‘long message’ (the ability to send...