Scribd
Upload
92 views

DLR Push API Specifications (Version 1.0.0) PDF

The DLR Push API sends delivery reports to client URLs with appended parameters including sender, recipient, message status, timestamps, IDs, and error codes. A POST request is made to the client URL with parameters specifying message details and delivery status. Response codes of 200 or 202 are considered successful, while other codes are failed requests.

Uploaded by

Albert Ninyeh
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
92 views

DLR Push API Specifications (Version 1.0.0) PDF

The DLR Push API sends delivery reports to client URLs with appended parameters including sender, recipient, message status, timestamps, IDs, and error codes. A POST request is made to the client URL with parameters specifying message details and delivery status. Response codes of 200 or 202 are considered successful, while other codes are failed requests.

Uploaded by

Albert Ninyeh
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

DLR Push API

Specifications
(Version: 1.0.0)
OVERVIEW
The DLR Push API sends the DLR to the Client’s URL.

URL
The URL for each client would look like ‘http://www.abc.net/Demo/Demo.aspx’ .
The parameters appended to the URL would be static. The parameters are explained below.

Request Parameters Description


1. sSender Source Address
2. sMobileNo Destination number of sent Message
3. sStatus Status of the Message (‘UNKNOWN’,’ACKED’,
‘ENROUTE’,
’DELIVRD’,’EXPIRED’, ’DELETED’,
’ UNDELIV’,’ACCEPTED’, ’REJECTD’)
4. dtSubmit Date-Time when the message is Submitted.
Date format should be ‘yyyy-mm-dd hh:mm:ss’
4. dtDone Date-Time at which delivery report is received.
Date format should be ‘yyyy-mm-dd hh:mm:ss’
5. sMessageId Unique identification for a message given at the time of
submission.
6. iCostPerSms Cost per SMS
7. iCharge Total credits deducted depending upon number of
message
parts
8. iMCCMNC Mobile country code and Mobile Network code
9. iErrCode No Error-0
Error-Respective Error code
Ex: Unknown Error-205

Error Codes

HTTP Status Description


Code
200 OK: The Request has succeeded.
The information returned with response is dependent on the
method used in the request
202 Accepted: The request has been accepted for processing, but
the processing has not been completed.

Note:
 The response codes other than 200 or 202 are not taken into considerations
and requests for such response codes considered as failed.
 The method used for posting delivery report onto the client’s URL is
POST.

You might also like