Nvia Technical Guides
SMS API Wiki 1.0
SMS API 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.2 HTTP with Content-Reply (Synchronous)

In this case the answer to the SMS would be the answer to the HTTP request, so the client should also have a working web server and provide Nvia with the URL where it will be listening for the requests.

The parameters that the listening script accepts (all optional) are:

  • Movil (Phone number)

  • Host: SC (short Code)

  • Operadora (Carrier)

  • texto (message’s text)

  • id_mensaje (Message ID), which identifies each message, just in case the client wants to have control over duplicated messsages, for example. “Id_mensaje”, is alphanumeric, and contains the initials of the servie provider (Carrier) followed by a number.

All parameters will be sent with the GET method. Answers will have the following format:

  • OK (space) text message

  • OKWAP (space) URL without “http://” (space) “texto wap”

  • OKBIN (space) Datos (space) Udh (space) Dcs

IP addresses, from where the requests will be done, will be the same as before. In case of an incorrect answer, Nvia will retry the request after one minute, then 2, 4, 8 and 16, storing the request at an error log if the last try wasn’t answered. In this case an e-mail will be sent to the person assigned as the "technical support" contact.

Last updated 1 year ago