Nvia Technical Guides
SMS API Wiki 1.0
SMS API Wiki 1.0VMS API Wiki 3.0Number Lookup Services Wiki 1.0
SMS API Wiki 1.0
SMS API Wiki 1.0VMS API Wiki 3.0Number Lookup Services Wiki 1.0
  • Basics
    • Glossary
  • 1. Sending SMS-MT
    • 1.1 Interfaces
      • 1.1.1 HTTP Request
        • Sending text, flash and binary messages
        • Sending WAP push messages
      • 1.1.2 JSON Request
        • Sending text, flash and binary messages
        • Sending WAP push messages
      • 1.1.3 Webservices
        • Sending text, flash and binary messages
        • Sending WAP push messages
      • 1.1.4 SMPP interface
        • About the SMPP interface
        • Date time formats for scheduled delivery and validity period
    • 1.2 Date time formats
    • 1.3 Error Codes
    • 1.4 Delivery Report Callback
  • 2. SMS - 2 Ways
    • 2.1 Sonic MQ
    • 2.2 HTTP with Content-Reply (Synchronous)
    • 2.3 HTTP (2 requests)
    • 2.4 Unanswered messages
    • 2.5 Delivery reports (DLR)
  • 3. SMS Certified by Blockchain
    • 3.1 SMS Certified by Blockchain
    • 3.2 Sending a SMS certified by blockchain
  • EXAMPLES
    • GitHub sendMtSms
Powered by GitBook
On this page
  1. 2. SMS - 2 Ways

2.5 Delivery reports (DLR)

For each MT, operators provide detailed information regarding the delivery: if the message was sucessfully delivered, if the message was not delivered because the end user didn’t have enough credit, if the message was rejected or deleted, etc.

Clients can configure a URL for the reception of this type of information.

When a SMS is received at the platform it is assigned a unique ID formed by a 2 character standard carrier identifier and a number. This ID is processed as “id_mensaje” (Message ID) and can’t be personalized.

Last updated 1 year ago