Status Updates is a service that we provide that allows you to monitor the progress of your messages through the SMS network. It is an alternative to requesting a succession of XML reports for yourself using the 'LoggedReport' method of our XML schema (see schema code 0310). We will provide information on the progress of your messages through the SMS network by sending XML in a HTTP POST to a URL of your choice.

Click here to see the XML schema used with Status Updates ...

Click here to see an actual example of XML provided by Status Updates ...

The XML Elements have the following interpretations:

• ID is the MessageID that is used internally to identify the message and may be used in correspondence with our support staff.
• Destination is the number to which the message was sent, in international format beginning with the country code.
• Text is the actual text of the short message
• Reference is the reference specified for the message batch. You may have chosen this yourself, or it could be the 2sms default value which gives the time at which the message was sent.
• DateReceived is the date at which this update was received by us in MM/DD/YYYY HH:mm:ss format
• Status is the status to which the message is being updated, as used in our standard reports. Click here for more information on the different message status values (you will need to be logged into your 2sms account) ...
  
• Reason is the Error or Success reason reported to us from the SMS network and provides additional information to complement the Status.

You are charged 0.25 credits for each update that you receive. You should expect to receive up to four updates per message (e.g. when it was first received by the SMS network, when it is finally delivered and updates about its progress on the way.) This means that the cost of reporting using this method is around 1 credit per message.

Status Updates is an alternative to requesting a succession of XML reports for yourself using the 'LoggedReport' method of our XML schema (see schema code 0310). Your decision on which to use may be based on which method best suits your IT setup (e.g. you will need to create a special listener page on a web-server to use delivery receipts. However, if your decision on which method to use for reporting is based on cost rather than practical matters it makes sense to use status updates if you are running four or more reports for each message you send.

Of course many users will simply choose to request XML reports from 2sms at less frequent intervals and lower their reporting costs this way. This is a perfectly sensible approach to the problem, as the credit charge is intended to limit access to a valuable resource.