Bulk SMS delivery reports
Automatic delivery reports push
In order to receive automatic delivery reports pushes,
you need to provide us with:
- HTTP or HTTP push address
The URL on which you will be receiving our delivery notifications.
- POST or GET method
If we shall transmit the delivery reports by either HTTP-POST or HTTP-GET method.
This method needs to be provisioned by us. Please contact us if you wish to use the automatic delivery reports push.
The delivery push consists of the following parameters:
(Recipient number with leading zeros)
(MESSAGEID from MT submission)
(Status according operator / SMSC reply)
Example: BUFFERED 107
Example: NOT DELIVERED 107
(Descriptional text for STATUS parameter)
Example: Various texts
(Timestamp when notification was received)
Example: 30.12.2005 18:30:45
Manual request of delivery report
This method can be used for self service accounts.
In order to pull delivery report information,
you should send requests to either:
- HTTP Reception Gateway
- HTTPS Reception Gateway
Manual request parameters
The HTTP POST transmission string is composed of
keywords with associated values, separated by
equals sign (=). All such keyword=value pairs are
connected with standard HTTP POST character &.
The hole HTTP request should be URL encoded.
The MT request consists of the following parameters:
(Fixed command value)
(Your account name)
(Your account password)
(The MESSAGEID from the MT submission)
- NUMBER (optional)
(The recipient number from the MT submission. This parameter can be omitted if you are sending less than 1 SMS per second. If you send more than 1 SMS per second you might have several same messageids in the format YYMMDDHHMMSS and for exact tracking you will therefore also need to specifiy the recipients number)
Manual request result codes
Upon reception of the MT POST transmission string,
the gateway will respond back with one of the following
possible result codes:
- 01 STATUS:"DELIVERED"[lf]
TIMESTAMP:"DD.MM.YYYY HH:MM:SS" [lf]
DESCRIPTION:"Message for 079..., with identification YYMMDDHHMMSS
has been delivered on YYYY-MM-DD at HH:MM:SS."
- 02 MESSAGEID NOT FOUND
Error: The MESSAGEID could not be found..
If no delivery, forwarding or buffered report was yet received, this error will also be returned. You should only start to pull delivery reports a few seconds after you have sent the MT.
- 90 INVALID ACCOUNT
Error: The account doesn’t exist
- 91 INVALID PASSWORD
Error: The password is incorrect
- 92 INVALID PARAMETERS
Error: Mandatory parameters are missing
- 94 UNTRUSTED HOST
Error: Tracking host is not granted access
For self service accounts, you can configure the trusted hosts from within the administration section.
Shell script examples using CURL
You can use any software or programming language for accessing the HTTP / HTTPS tracking interface. Below we are providing example scripts of the most basic part, using CURL for the request.
For the script examples, you will need to install the CURL version corresponding to your operating system:
- Visit the CURL download page and download the version for your needs
Shell scripts for tracking delivery reports
Linux/Unix/Mac OS X shell scripts
./tracksms.sh Account Password MessageID [NUMBER]
Windows shell scripts
tracksms.bat Account Password MessageID [NUMBER]