Delivery receipts for MT and MO SMS messages

If required, SMS API can automatically send delivery receipts (DR) to your server in response to both MT SMS and MO SMS messages. The original MT SMS and MO SMS messages must include a valid <receiptUrl> before the SMS API can post a DR.

The following conditions apply:

• If required, MO SMS is enabled on the customer's SMS API configuration
• The source device MSISDN is included on the SMS Allowlist
• If an optional IP address Allowlist exists, the source device is included

Authentication

• None

Response text/html

Parameters	Description
messageid	A user-generated unique message identifier for tracking the original message
referenceid	Eseye internally generated reference
statuscode	Delivery status code
status	Either: delivered – The original message was delivered successfully failed – No delivery confirmation was received

Example

http://ota.yourcompany.net/callback.php?messageid=9946e3025608c7106944658dfb1318a8&referenceid=3fd515e674835bb233538f9d218a31d9&statuscode=delivered&status=delivered