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. 3. SMS Certified by Blockchain

3.2 Sending a SMS certified by blockchain

The Nvia Platform allows certified messages to be sent using both the HTTP GET and the HTTP Post interfaces. The base URL to which partners must request the sending of an SMS is the same as in Sending a SMS-MT:

http://www.panelsms.com/httpinput/input.php?
Copy

Parameters

Add the following parameters in the base URL:

PARAMETER NAME
DESCRIPTION
REQUIRED

certificate

Value [0] when certified is false (not certified)

Value [1] when certified is true

Yes

bizname

Message sender

Yes

site

Place where the MO was generated (App, Web, etc.)

Yes

cif

Message sender ID based on personal or company identification number (DNI, CIF, TIN etc.)