17 Dec Delivery Receipt

 

Telintel will send a delivery receipt (where applicable) for each SMS submission. In order for Telintel to return this result a Callback URL must be reported. Account Administrators can log into their Telintel Managed Messaging Platform account and add a Delivery Receipt Callback URL in the “My Profile > Settings” section.

 

HTTP Methods

The request parameters are sent via HTTP POST to the Delivery Receipt CallBack URL on the account. Telintel will be expecting a 200 OK response, or it will keep retrying until either the Delivery Receipt expires (up to 72 hours) or the maximum amount of attempts is reached (up to 10 attempts).

 

Request Parameters

The Telintel Delivery Receipt request includes the following parameters:

In the header of the request for “messageId

Parameter Name

messageId

Description

The unique message ID reference assigned to each submitted SMS.

Variable Type

String

Mandatory?

YES

 

In the header of the request for “dlrDeliverInitTStamp

Parameter Name

dlrDeliverInitTStamp

Description

Timestamp of when the delivery receipt is initially sent, used in the following format:
yyyy-MM-dd HH:mm:ss.SSS-z
Example:

 

Variable Type

String (Date)

Mandatory?

YES

 

In the body of the request (mblNetworkReceiveTStamp):

Parameter Name

mblNetworkReceiveTStamp

Description

Timestamp of when the notification is received from the mobile network, used in the following format:
yyyy-MM-dd HH:mm:ss.SSS-z
Example:

 

Variable Type

String (Date)

Mandatory?

YES

 

Request Parameters for “requestId“:

Parameter Name

requestId

Description

An integer that represents a unique reference ID of the request (all

transactions).

Variable Type

Number, Integer

Mandatory?

YES

 

Request Parameters for “recipientNumber“:

Parameter Name

recipientNumber

Description

The recipient MSISDN number where the initial message was sent.

Variable Type

String

Mandatory?

YES

 

Request Parameters for “deliverReceiptStatus“:

Parameter Name

deliverReceiptStatus

Description

The Status related to the inbound delivery receipt.

Variable Type

String (Enumerated)

Mandatory?

NO

 

Request Parameters for “errorCode“:

Parameter Name

errorCode

Description

An integer representing the return code of the response / error.

Please reference Response Codes table Anex A

Variable Type

Integer

Mandatory?

NO

 

Request Parameters for “messagePrice“:

Parameter Name

messagePrice

Description

The price of the message (in U.S. Dollars).

Variable Type

Number, Double

Mandatory?

NO

 

Request Parameters for “mccmnc“:

Parameter Name

mccmnc

Description

Identifies the mobile network’s MCCMNC code in relation to the message, used in the following format: MCC/MNC

Variable Type

Enum

Mandatory?

NO

 

The request body will contain a JSON object.

 

3.3 Delivery Receipt Status Table

 

Message Status

Description

DELIVERED
The message was delivered to the destination.
EXPIRED
The message validity period has expired.
DELETED
The message has been deleted.
UNDELIVERABLE
The message is undeliverable.
ACCEPTED
The message was accepted.
UNKNOWN
The message is in an invalid status / Unknown status.
REJECTED
The message was rejected.