Forthnet Mobile Platform - groupsms http interface v1.0 1 / 9
|
|
- Griffin Palmer
- 5 years ago
- Views:
Transcription
1 Table of Contents Introduction... 2 Requirements... 2 Connecting to Forthnet Mobile Platform... 2 Message submission... 3 Client Request... 3 Parameters... 4 Parameter user... 4 Parameter pass... 4 Parameter sender... 4 Parameter dest... 5 Parameter message... 5 Parameter not... 6 Server Response... 6 Delivery Notifications... 7 Parameters... 8 Parameter type... 8 Parameter msgid... 8 Parameter status... 8 Parameter timestamp... 9 References... 9 Forthnet Mobile Platform - groupsms http interface v1.0 1 / 9
2 Introduction The current document describes in detail the HTTP interface provided by Forthnet Mobile Platform for Short Message Service messages (SMSes) submission. The interface enables client applications to send SMSes to subscribers of mobile networks by conveying the message data in requests according to the HTTP protocol (for further information on the HTTP protocol please refer to [1] in References). The requests are received and parsed by the server and the appropriate SMSes are generated and delivered to the mobile subscribers. The Forthnet Mobile Platform supports only text SMSes for the time being. In addition, the Forthnet Mobile Platform supports delivery notifications, i.e. messages that convey the status of SMS transmission (e.g. confirmation that the SMS has been received by the recipient s handset). If a customer is enabled to use this feature, he can request delivery notifications on per SMS basis. If a submitted SMS requests for delivery notifications, the notifications related to the message are collected from the mobile network and are forwarded via HTTP to the client s server. Towards this, a client that desires the delivery notifications feature must provide to Forthnet his server details (i.e. the URL of the page that handles the notifications on the client s server) when his account is going to be activated. The Forthnet Mobile Platform supports both GET and POST methods for HTTP requests submission. This document describes the communication with Forthnet Mobile Platform for: SMS submission via HTTP GET requests, and Notifications Forwarding via HTTP GET requests. Requirements The Forthnet Mobile Platform Bulk SMS http interface doesn t impose any requirements on the operating system (MS Windows, UNIX, Linux, etc.) of the machine where the client application runs. On the contrary, the client application must only support the ability to send standard HTTP GET or POST requests. In addition, in order a user to be allowed to send SMSes via the interface, he must have an account. Connecting to Forthnet Mobile Platform In order a client application to send an HTTP request to the Forthnet Mobile Platform, it has to establish a (TCP/IP) connection with the server. The server s address is the following: NOTE: The AThost and ATport information are revealed upon the purchase of the service. Forthnet Mobile Platform - groupsms http interface v1.0 2 / 9
3 Message submission Client Request In order to submit an SMS using the GET HTTP method, a URL in the following format must be generated: =valuen Example URL ve+a+nice+day&user=demo&pass=demo Toward this, the client application must connect to the server (AThost:ATport) and send a GET request (formatted as follows): GET /smsc/insms?param1=value1¶m2=value2& ¶mn=valuen HTTP1/1\n Host: AThost:ATport\n \n (Three lines total. It is mandatory to send the third blank line) Please note that the values of the parameters must be URL encoded (see [2] in References). So, the value %2B of parameter dest in the above example URL is the encoding of The following table presents some special character mappings according to URL encoding: Character URL encoding & %26 + %2B % %25 # %23 Blank space %20 = %3D? %3F ; %3B \n %0D Forthnet Mobile Platform - groupsms http interface v1.0 3 / 9
4 Parameters Table below contains a list of available parameters: Parameter Description M/O Type Valid Values / Limitations user Account username M String - pass Account password M String - sender Message sender O 1 Numeric or String dest Message destination(s) M Comma separated numstring list If it's a numeric sender of type shortcode we expect 3-6 digits length. If it s an alphanumeric sender we expect up to 11 latin chars (space included). If it s an MSISDN sender we expect it in international format starting with +. One up to 100 target MSISDNs in international format (starting with + ), i.e , message Message Body O 2 String Max 160 chars Message Boolean or The Boolean values true/false or the Integer not notification O Integer values 0, 1, 2 or 3 indicator NOTE 1: Parameters user, pass, sender, dest and message are mandatory while parameter not is optional. Here is an explanation on how you should use these parameters. Parameter user (mandatory) The client s assigned username. Parameter pass (mandatory) The client s assigned password. Parameter sender (mandatory) The originator of the message. Could be either numeric (maximum 20 characters) according to the international GSM format (only the format with the leading plus is allowed, i.e ) or alphanumeric (maximum 11 characters). Forthnet Mobile Platform - groupsms http interface v1.0 4 / 9
5 Examples sender=54546 sender=forthnet sender= Parameter dest (mandatory) The dest parameter is used to specify the destination GSM number(s) of the SMS. A comma-separated list could be used to specify more than one destination number. The maximum allowed number of destinations is 100. Each destination number must not be longer than 20 characters and it must be written in international format with the leading plus sign (e.g. the greek GSM number must be written as ). The 00 international format (e.g ) is not allowed for this field. Example (one destination) dest= Example (multiple destinations) dest= , Please note that according to the URL encoding, the plus character ( + ) corresponds to %2B. So if is to be used as message destination, it must be encoded as %2B Parameter message This parameter sets the Short Message text. Its length must not exceed the limit of 160 characters. The allowed characters can be: 1. All uppercase or lowercase Latin letters 2. All uppercase or lowercase Greek letters 3. All decimal digits 4. Characters `~!@#$%^&*()_+-={} []\: ; <>?,./ Forthnet Mobile Platform expects the value of message parameter in UTF-8 encoding. Of course, since it s on URL it must be URL-escaped, i.e. special characters like the ones shown in the table above must be transformed according to URL-encoding. Forthnet Mobile Platform - groupsms http interface v1.0 5 / 9
6 Parameter not (optional) If this parameter is used with true value, then delivery notifications are requested for the corresponding SMS according to client s account configuration. The default value of parameter not is false. If a user that is not enabled to use the delivery notifications feature sets this parameter as true, the message will be sent but no delivery notification will be submitted. Server Response Upon the receipt of an SMS submission request, the server parses the parameters, performs the required checks and sends back a response. The information regarding the submission status is propagated in the first line of the response body. It includes a status code and a status description. The possible values of the (Code, Description) pair are presented in the table below. If the not parameter is enabled, then the response includes an additional line ( msgid= ) with a message id (whose type is String). This message id must be used to correlate delivery notifications with sent messages (see Delivery Notifications section bellow). If a message has multiple recipients, then a (comma-separated) list of message ids is returned. Each message id corresponds to an SMS sent to one of the recipients. The message ids correspond to the message destinations according to the order that the destinations were contained in the destination list of the request. So, if a valid message submission request with dest= , generates a response with msgid=1234,1235 then 1234 is the msgid that corresponds to the SMS sent to the first recipient ( ) while 1235 corresponds to the SMS sent to A sample server response (including the message id information in the body) is the following: HTTP/ OK\n Content-Type: text/plain; charset=iso Content-Length: 23 \n \n 001 OK\n msgid=1343,1344\n Forthnet Mobile Platform - groupsms http interface v1.0 6 / 9
7 The possible (Code, Description) values included in a server response are shown in the following table: Status Code Status Description 001 OK 101 Missing Parameter 102 Illegal Parameter 103 Invalid SMS Number Format 104 Internal Server Error 105 Unauthorized User 106 Unauthorised IP Address 107 Account Disabled 108 Max Message Length Exceeded 109 Invalid Message Text Delivery Notifications Upon the receipt of a delivery notification, Forthnet Mobile Platform will forward it to the specified client s server. Towards this, an HTTP GET request of the following format will be generated and forwarded to the client s server: GET /customer_page?type=2&msgid=id&status=stat×tamp=t HTTP/1.1\n Host: CustomerServerHost:CustomerServerPort\n \n Example GET /not.php?type=2&msgid=1234&status=smscrcv×tamp= %3A56%3A HTTP/1.1\n Host: :80\n \n The client script must reply by using a string which begins with OK or NOK. Otherwise, the server will continue to send the message assuming that the initial attempt was unsuccessful. Forthnet Mobile Platform - groupsms http interface v1.0 7 / 9
8 Parameters An overview of the parameters contained in a delivery notification HTTP Request is shown in the following table. Please note that all parameters are mandatory and will always be included in the HTTP Request. Parameter Type Possible Values / Comment type Integer always set to 2 msgid String - status String delivery notifications: SMSCRCV SMSCRJT HSRCV HSRJT SMSCFWD SMSCEXP timestamp String yyyy-mm-dd HH:mm:ss.SSS Parameter type This parameter has always the value 2 when the HTTP Request contains a delivery notification. It is used in order the customer s server to able to distinguish notifications from MO SMSes that might be as well forwarded via HTTP GET requests (which have the parameter type set to 1, for more information see [3] in References) to the same page of the client s server. Parameter msgid The parameter msgid identifies the SMS sent by the client that the delivery notification refers to. It is the msgid value that customer collected on the MT submission. Parameter status The status field contains information regarding the status of the transmission of an SMS. As mentioned above, two types of notifications are supported, delivery notifications and billing ones. The latter are valid only in the case of MT billing SMSes. The delivery notification statuses supported are: SMSCRCV denotes that the SMS was received by the SMSC that serves the destination handset. SMSCRJT declares that the SMS was rejected by the SMSC, i.e. due to invalid destination number. HSRCV means that the SMS was successfully delivered to the recipient s handset. HSRJT refers to the case of unsuccessful delivery, for reason other than expiration of validity period. Forthnet Mobile Platform - groupsms http interface v1.0 8 / 9
9 SMSCFW deals the case where an SMS has to be forwarded from the operator that was chosen to submit it, to another operator to which the subscriber belongs. SMSCEXP denotes the case where the SMS validity period has expired. Parameter timestamp The exact timestamp when the notified event occurred in YYYY-MM-DD HH:MM:SS.SSS format. NOTE: All notification timestamps are in UTC. References [1] RFC 2616: Hypertext Transfer Protocol HTTP/1.1 [2] RFC 1738: Uniform Resource Locators (URL) [3] Forthnet Mobile Platform - Premium SMS http interface Forthnet Mobile Platform - groupsms http interface v1.0 9 / 9
LINK Mobility SMS REST API MT and Delivery Reports Version 1.3; Last updated September 21, 2017
LINK Mobility SMS REST API MT and Delivery Reports Version 1.3; Last updated September 21, 2017 For help, contact support@linkmobility.com The most up-to-date version of this document is available at http://www.linkmobility.com/developers/
More informationSMS Outbound. SMTP interface - v1.1
SMS Outbound SMTP interface - v1.1 Table of contents 1. Version history... 5 2. Conventions... 5 3. Introduction... 6 4. Gateway connection... 7 4.1 E-mail message format... 7 4.2 Header section... 7 4.3
More informationSMS Outbound. HTTP interface - v1.1
SMS Outbound HTTP interface - v1.1 Table of contents 1. Version history... 5 2. Conventions... 5 3. Introduction... 6 4. Application Programming Interface (API)... 7 5. Gateway connection... 9 5.1 Main
More informationSMS-Bulk Gateway HTTP interface
SMS-Bulk Gateway HTTP interface Release 3.0.0 2001-2017 SmsItaly.Com 1 1 Introduction 1.1 Summary Only authorized users can submit SMS messages for delivery by one of the following methods: - Internet
More informationIntegrating with Cellsynt's SMS gateway via HTTP interface (technical documentation)
Integrating with Cellsynt's SMS gateway via HTTP interface (technical documentation) Integrating with Cellsynt's SMS gateway via HTTP interface (technical documentation) Table of Contents Part I Introduction
More informationAll requests must be authenticated using the login and password you use to access your account.
The REST API expects all text to be encoded as UTF-8, it is best to test by sending a message with a pound sign ( ) to confirm it is working as expected. If you are having issues sending as plain text,
More informationResponse: Note: Please define Dynamic Value in ##Field## The following are the parameters used: For Unicode Message:
For Unicode Message: Promotional Unicode Message API http://cloud.smsindiahub.in/vendorsms/pushsms.aspx?user=youruserid&password=yourpassword& msisdn=919898xxxxxx&sid=senderid&msg=पर षण स द श &fl=0&dc=8
More informationQuriiri HTTP MT API. Quriiri HTTP MT API v , doc version This document describes the Quriiri HTTP MT API version 1 (v1).
Quriiri HTTP MT API This document describes the Quriiri HTTP MT API version 1 (v1). Sending messages Request types Security Request parameters Request examples JSON POST GET Response JSON response example
More informationWay2mint SMS Mobile Terminate (MT) API Guide for HTTP HTTPS
Way2mint SMS Mobile Terminate (MT) API Guide for HTTP HTTPS The content of this document are copyright and remain the property of. This document is not to be reproduced in any form, whether electronic,
More informationIntegration Guide Xura Messaging SMTP- Interface
Integration Guide Xura Messaging SMTP- Interface Version 1.3.0 Content is subject to change Xura Secure Communications GmbH Tel.: +49 89 201 727 0 e-mail.: asc-support@xura.com All rights reserved. This
More informationcellip CELLIPS SMS INTERFACE DESCRIPTION HTTP GET INNEHÅLLSFÖRTECKNING
INNEHÅLLSFÖRTECKNING Innehållsförteckning... 1 1 Introduction... 2 1.1 Scope... 2 2 HTTP Get interface... 2 2.1 Mobile Terminated Messages... 2 2.1.1 Usage... 2 2.1.2 Parameters... 2 2.1.3 Codes... 4 2.1.4
More informationIntegration Guide Xura Messaging HTTP-Interface
Integration Guide Xura Messaging HTTP-Interface Version 2.1.5 Content is subject to change Xura Secure Communications GmbH Tel.: +49 89 201 727 0 e-mail.: asc-support@xura.com All rights reserved. This
More informationSMS Submit Interface description HTTP Version 1.5
SMS Submit Interface description HTTP Version 1.5 This document is intended for application developers with knowledge about the HTTP protocol. Document history Version Description 1.5 Spelling error corrected
More informationAPI Documentation. Release Version 1 Beta
API Documentation Release Version 1 Beta Document Version Control Version Date Updated Comment 0.1 April 1, 2016 Initialize document 1 Release version PROMOTEXTER V3 BETA - API Documentation 1 Table of
More informationAPI Specification Doc
API Specification Doc (SMS System Gateway) Version Date Description 1.0 01-Nov-2017 Initial draft 1.1 18-Feb-2018 Updated to include Delivery report call back options 1.2 10-Apr-2018 Appended API to include
More informationGatesms.eu Mobile Solutions for Business
TECHNICAL SPECIFICATIONS XML Web API GATESMS.EU, version 1.1 Prepared by: Gatesms.eu Contents Document version history...3 Security...3 General requirements...3 HTTP transmission security mechanism...3
More informationTechnical Guide. REST API for Mobile Outbound SMS
Technical Guide REST API for Mobile Outbound SMS Munich +49 89 202 451 100 Singapore +65 6478 3020 London +44 207 436 0283 San Francisco +1 415 527 0903 sales@tyntec.com www.tyntec.com Table of Contents
More informationWired 2 Wireless Technology Solutions API Help Document Copyright Introduction. 2. Parameter list
1. Introduction Wired 2 Wireless Technology Solutions offers an easy way to send and receive messages via its built-in webserver using HTTP. In this document you will learn how to send SMS, check delivery
More informationCloud SMS API Guide. Version 5.1
Cloud SMS API Guide Version 5.1 Cloud API Guide v5.1 Page 1 of 18 Table of Content 1 Overview 1 2 MACH Push Messaging 2 3 MT API Details 3 3.1 Send Message 3 3.2 Send Long Concatenated Messages 8 4 MO
More informationMessage parameter details
HTTP API for Message Forwarding (SMS India Hub Gateway Version 1.1) Overview... 2 Introduction... 2 Messaging... 3 Message parameter details... 4-7 Error Codes... 8 Contact Details... 9 Overview This document
More informationWay2mint SMS Mobile Terminate (MT) API Guide for HTTP / HTTPS
Way2mint SMS Mobile Terminate (MT) API Guide for HTTP / HTTPS 10/1/2009 Way2mint Services Prepared by: Mohit Jaswani Copyright Way2mint Services The content of this document are copyright and remain the
More informationOverview Introduction Messaging Error Codes Message parameter details Contact Details... 7
HTTP API for Message Forwarding (SMS Lane Gateway Version 1.1) Overview... 2 Introduction... 2 Messaging... 3 Error Codes... 4 Message parameter details... 5-6 Contact Details... 7 1/7 Overview This document
More informationRevision: 50 Revision Date: :43 Author: Oliver Zabel. GTX Mobile Messaging SMS Gateway Interface Simple HTTP API Manual
Revision: 50 Revision Date: 09.06.17 14:43 Author: Oliver Zabel GTX Mobile Messaging SMS Gateway Interface Simple HTTP API Manual Table of Contents Table of Contents... 2 Introduction... 3 Sending SMS...
More informationeservices channel-any_name_for_sms Section
eservices channel-any_name_for_sms Section 6/30/2018 channel-any_name_for_sms Section default-reply-address driver-classname inbound-route password reconnection-timeout session-by-address session-by-text
More informationHTTP API-HELP DOCUMENT
PARAMETER DEFINITION S.NO PARAMETER PARAMETER VALUE PARAMETER NAME DESCRIPTION 1 User Test User User name of the 2 Passwd Test Password Password of the account 3 Sid DEMO Sender id Destination Mobile 4
More informationPCCW mobile SMS Web Access 2.0 User Guide
PCCW mobile SMS Web Access 2.0 User Guide Version 2.1.2 11 March 2011 Version: 2.1.2 Table of Content 1 Introduction... 4 2 General... 5 2.1 Getting started... 5 2.2 Login/Logout... 5 2.3 Switch between
More informationLINK Mobility SMS REST API MO messages Version 1.1; Last updated June 07, 2017
LINK Mobility SMS REST API MO messages Version 1.1; Last updated June 07, 2017 For help, contact support@linkmobility.com The most up-to-date version of this document is available at http://www.linkmobility.com/developers/
More informationUSSD HTTP API SPECIFICATION Version 1.0 Teletalk Bangladesh Limited
USSD HTTP API SPECIFICATION Version 1.0 Teletalk Bangladesh Limited Latest version of this document can be obtained from: http://www.nixtecsys.com/ussd/ugw- teletalk- http- api.pdf 2 This page has been
More informationERMES. Technical Specification for ex MPAY services integration. version /10/2018
ERMES Technical Specification for ex MPAY services integration version 1.7 26/10/2018 Summary 1.Changes...3 2.Introduction...4 2.1.Glossary...4 3.ERMES API Overview...5 3.1.Protocol...6 4.ERMES API...9
More informationWE POWER YOUR MOBILE WORLD FTP INTEGRATION MANUAL
FTP INTEGRATION MANUAL 1 CONTENTS INTRODUCTION... 3 CONNECTIVITY... 3 CONNECTION PROCESS... 4 INTERFACE... 5 archive folder... 6 errorprocessing folder... 6 idle folder... 6 incoming folder... 6 mobileoriginated
More informationREST SERVICE. Web Services API Version 1.5
REST SERVICE Web Services API Version 1.5 The information contained within this document is the property of PageOne Communications Ltd and may not be copied used or disclosed in whole or in part, except
More informationHTTP API. https://www.smsn.gr. Table of Contents
HTTP API https://www.smsn.gr Table of Contents Send SMS...2 Query SMS...3 Multiple Query SMS...4 Credits...5 Save Contact...5 Delete Contact...7 Delete Message...8 Email: sales@smsn.gr, Τηλ: 211 800 4200,
More informationAPI Spec Sheet For Version 2.5
INTRODUCTION The Wholesale SMS API is ideally suited for sending individual sms messages and/or automated responses through our premium routes. To send bulk messages through the API you can set your server
More informationSMS Pro/Billing Pro. Interface specification. Version 3.0.1
SMS Pro/Billing Pro Interface specification Version 3.0.1 Copyright Telenor Sverige AB 2008 Contents: 1 Introduction... 3 2 Protocols for interconnection... 3 3 Content format... 3 4 XML References...
More informationBulk HTTP API Specification
Bulk HTTP API Specification (Document Version 1.0) (This Document gives details on how to send messages via the Bulk HTTP API for the CloudSMS Gateway) HTTP API to submit messages to CloudSMS http://developers.cloudsms.com.ng/api.php?userid=xxxx&password=yyyyy&type=y&destinati
More informationtext2reach2 SMS API Sep 5, 2013 v1.1 This document describes application interface (API) between SMS service provider (SP) and SMS gateway (SMSGW).
text2reach2 SMS API Sep 5, 2013 v1.1 This document describes application interface (API) between SMS service provider (SP) and SMS gateway (SMSGW). Table of Contents API Interface Types...3 Bulk SMS interface...3
More informationRouteMobile Mobile Client Manual for Android Version: 2.0
RouteMobile Mobile Client Manual for Android Version: 2.0 Route Mobile Limited 2018. All rights reserved 1 Contents Installation... 3 Getting Started... 5 Login Page... 6 Main Screen... 7 Send SMS... 9
More informationHTTP API Specification V2.7
HTTP API Specification V2.7 Version information Version Comment Date V2.7 Added testsms call 2017-08-09 V2.6 HTTPS information added 2016-12-10 Added error code 4007 V2.5 Changed endpoints 2016-12-09 Added
More informationSMSCenter. SMSCenter API
www.smscenter.co.il SMSCenter Multi Messaging Software Server SMS / MMS / IVR / WAP Push SMSCenter API SMSCenter API The software described in this book is furnished under a license agreement and may be
More informationUser Guideline v 2.1. For assistance please contact Grapevine on or
SMS Broadcast User Guideline v 2.1 Support : Feedback : For assistance please contact Grapevine on +27 21 702 3333 or email support@vine.co.za Please email info@vine.co.za with your comments and feedback
More informationversion 2.0 HTTPS SMSAPI Specification Version 1.0 It also contains Sample Codes for -.Net - PHP - Java
HTTPS SMS API SPEC version 2.0 HTTPS SMSAPI Specification This document contains HTTPS API information about - Pushing SMS, - Pushing Unicode SMS, - Scheduling SMS - Checking SMS credits, Version 1.0 -
More informationHTTP Specification Version 1.83
HTTP Specification Version 1.83 1. HTTP URL link 2. Sending Text Message 3. Sending Flash Message 4. Sending Unicode Message 5. Sending Binary Message 6. Sending 2D Barcode Message 7. Check for credits
More informationezeesms URL API Documentation
ezeesms URL API Documentation 1 1. ABOUT COMPANY: Pinnacle Teleservices Pvt. Ltd. is a leading Cellular IT Solutions Company established in 2003 and awarded as ISO 9001: 2008 Certified Company, traveled
More informationFront Gateway Product Description for the connection between the SMS gateway and customer
Front Gateway Product Description for the connection between the SMS gateway and customer Applies to: SMS Gateway Standard SMS Gateway Proff SMS Gateway PSK Development Manual v.2.22 2017-05-05 Side 1
More informationHTTP API - HELP DOCUMENT
1. INTRODUCTION This document is to provide help and illustrations to users who wish to delivery SMS using the SMSCountry SMS Gateway via the HTTP Protocol. Accessing gateway through HTTP API is one of
More informationHTTP Based Unified API
HTTP Based Unified API SMS GATEWAY Issue 5.0 June 2017 1 HTTP Based Unified API HTTP ACCESS MODEL INTRODUCTION The platform exposes a HTTP interface to its SMS Gateway. The SMS Gateway can be used for
More informationPROFESSIONAL SMS APP CENTER USER MANUAL
2017 WWW.TEXTGHANA.COM Silky I.T. Production 0245701001 textghana@gmail.com info@textghana.com PROFESSIONAL SMS APP CENTER USER MANUAL Professional SMS is designed to send large customised SMS volumes
More informationNIC SMS SERVICE INTEGRATION
Overview NIC Messaging Division has set up new SMS Gateway services. In order to integrate your application and to access different services like reports and statistics please refer to below steps. To
More informationMyMobileAPI. mymobileapi.com. Windows Service Usage
MyMobileAPI mymobileapi.com TABLE OF CONTENTS Assumptions... 3 Database Structure... 4 Database... 5 User Table... 5 Queue Table... 6 Sent Table... 7 Reply Table... 8 Shortcode Table... 9 Example 1...
More informationHLR Lookup Service (Release 1.1.0)
1. Introduction 1.1. Summary This document will illustrate the HLR Lookup Service (or Network Query) 1.2. Scope The information contained in this document may be used by all third parties that need to
More informationXML API SMS GATEWAY. Issue 2.0 Dec XML API
XML API SMS GATEWAY Issue 2.0 Dec 2016 1 XML API XML API INTRODUCTION The XML API allows sending SMS through XML queries to our SMS Gateway. The SMS Gateway can be used for sending following types of SMS.
More informationQuenbec inc # henri bourassa H3L-3N3 Montreal, QC,Canada Toll free: Mobile Https://canadiansms.
HTTP PROTOCOL SPECIFICATIONS VERSION 3.0 Contents Http api of canadiansms.com.....what to find in this http api...how to send sms....how to check your credits.....how to download your reports....how to
More informationHTTP Interface API. for SMS Services. Version 2. Claude ICT Poland Sp. z o. o.
Version 2 HTTP Interface API for SMS Services Claude ICT Poland Sp. z o. o. WWW.TELECUBE.PL Table of Contents 1. Foreword...2 2. Revision History...2 3. Introduction Please Note...3 a. Communication Protocol...
More informationSMS Mobile Termination (MT) API Guide for HTTPS
SMS Mobile Termination (MT) API Guide for HTTPS The content of this document are copyright and remain the property of National Informatics Centre. This document is not to be reproduced in any form whether
More informationedocs Aero Users Management
edocs Aero Users Management Description edocs Aero Users Management System allows Company Admin to sync and control Users with other systems, by importing a CSV file. Admin can Add Users Change Users status
More informationAPI-SMS HTTP/GET Interface Ref Push SMS, Balance, ACKs. April 18, 2017 v1.12
Ref. 17041802 - Push SMS, Balance, ACKs. April 18, 2017 v1.12 Index Page 1 Introduction 3 1.1 Changelog 3 2 Send SMS messages (MT) 4 2.1 Required information 4 2.2 HTTP/GET Messaging 4 2.3 HTTP/GET Variables
More informationExcel-SMS Enotified. Excel-SMS Help Manual
Enotified Help Manual 7/7/2012 Contents 1. What is the excel-sms User Guide?... 2 2. Getting Started with excel-sms... 2 3. About the excel-sms Interface... 3 4. How to Send an SMS... 4 4.1 Sending One
More informationSMPP Server User Guide
SMPP Server User Guide Whilst the greatest care has been taken to ensure the accuracy of the information contained herein, NRSGATEWAY does not warrant the accuracy of same. NRSGATEWAY expressly disclaim
More informationPro Solutions Interface specification
Interface specification Version 3.1.0 Copyright Telenor Sverige AB 2010 Contents: 1 Introduction...3 2 Protocols for interconnection...3 3 Content format...3 4 XML References...4 5 Abbreviations...4 6
More informationSOAP API. The correct URL has been hidden. Please contact your account manager for the full URL information.
SMS Help Guides TNZ Group Limited sales@tnz.co.nz +64 9 9293000 +64 9 522 8839 SOAP API SOAP is a simple way of sending SMS/TXT messages via the internet. It is a great solution for integration into existing
More informationBozoka mobilforward manual
Bozoka mobilforward manual Bozoka.com AB Tegnérgatan 28, Stockholm, Sweden Contact support@bozoka.com Last updated November 2, 2011 1 Introduction In short, mobilforward is an application used for forwarding
More informationWeb Service API for. Document version 0.5 (2015-8) (Draft)
Web Service API for Document version 0.5 (2015-8) (Draft) Team Mobilis Co., Ltd Email: technical@teammobilis.com Technical hot line: 089-668-9338 (Vorapoap) 2 Contents HOW TO CREATE WEB APP USERNAME/PASSWORD?...
More informationQuick Answers. You may create any Sender ID for the transactional route, provided the Sender ID should be of 6 alpha characters only.
Quick Answers Text SMS How to choose Bulk SMS sender ID? You may create any Sender ID for the transactional route, provided the Sender ID should be of 6 alpha characters only. What is an Opt-Out SMS? How
More informationUser Configuration Settings
CHAPTER 11 This chapter contains settings that you configure when you add and update users. After you become familiar with the Cisco Voice Provisioning Tool, consider printing this chapter to use as a
More informationSMS HTTP API DOCUMENTATION December 2012
SMS HTTP API DOCUMENTATION December 2012 TABLE OF CONTENTS 1.0) INTRODUCTION 3 2.0) SENDING NORMAL TEXT MESSAGES 4 3.0) SENDING UNICODE (UCS2) MESSAGES (MULTILINGUAL) 5 4.0) SENDING UDH HEADER MESSAGES
More informationAPI Integration Guide
API Integration Guide Introduction SULU Mobile Solutions API is a programmable SMS message service. It enables your in-house applications to have fully featured SMS capabilities using your favorite programming
More informationCLX Campaign Manager User Guide
CLX Campaign Manager User Guide The purpose of this Guide is to briefly describe usage of the Campaign Manager Portal. This tool is used to ingest US Shortcode based Campaigns. This guide details what
More informationBME Data Feed Interface Specifications. Version: Related to: BME Data Feed Release 13.0
1.1 BME Data Feed s Document Name: BME Data Feed s Version: 3.00 Related to: BME Data Feed Release 13.0 Last Updated BME Data Feed s Page 2 of 2 REVISION HISTORY This section refers to the major changes
More information1. Sending SMS using any client 2. Outlook Mobile Service (OMS) integrated SMS sending via outlook 2007 and 2010
SMS for Email Included in your RockendSMS package, is the ability to send SMS from any email client (EmailSMS) you are also able to send through Outlook Mobile Service (OMS) for Outlook 2007 and 2010 users.
More informationMessaging Service REST API Specification V2.3.2 Last Modified: 07.October, 2016
Messaging Service REST API Specification V2.3.2 Last Modified: 07.October, 2016 page 1 Revision history Version Date Details Writer 1.0.0 10/16/2014 First draft Sally Han 1.1.0 11/13/2014 Revised v.1.1
More informationAPI-SMS HTTP/POST Interface Ref Push SMS, Balance, ACKs. April 18, 2017 v2.15
Ref. 17041801 - Push SMS, Balance, ACKs. Index Page 1 Introduction 3 1.1 Changelog 3 2 Send SMS messages (MT) 4 2.1 Required information 4 2.2 HTTP/POST Messaging 4 2.3 XML format 4 2.4 XML examples 7
More informationActive Messenger User Guide
Active Messenger User Guide 0 2 8 Active Messenger User Guide Index 1. Login 2 1.1 Login to Vibe Active SMS 2 2. Set Up Your User Profile 3 2.1 Profile 3 2.2 Fill in the Invoice Contact details 4 2.3 Settings
More informationWebsense Secure Messaging User Help
Websense Secure Messaging User Help Welcome to Websense Secure Messaging, a tool that provides a secure portal for the transmission and viewing of sensitive, personal data in email. Use the portal to view
More informationMultiTexter.com Smart Messaging System. HTTP Application Programming Interface
MultiTexter.com Smart Messaging System HTTP Application Programming Interface 0. INTRODUCTION MultiTexter.com system offers various methods to send SMS messages. This document contains specifications for
More informationSMPP Gateway Manual. Route Mobile Limited. (Document version 1.5)
Route Mobile Limited SMPP Gateway Manual (Document version 1.5) This document describes how to interface to and use the Route Mobile Limited Messaging Platform for connecting to the Route Mobile Limited
More informationNew Dashboard - Help Screens
New Dashboard - Help Screens Welcome to the new Panacea Dashboard. This document aims to provide you with concise explanations of the menu system and features available to you as a Panacea user account
More informationSMPP Gateway Manual. SMPP Gateway Manual Page 1
SMPP Gateway Manual SMPP Gateway Manual Page 1 Introduction The RouteMobile Messaging Platform uses the SMPP v3.4 Protocol Specification Issue 1.5, However it has been designed to be backward compatible
More informationSMS Relay. API Documentation SPLIO - SPRING Contact and Campaign SMS Relay API - EN v1.2.docx
SMS Relay API Documentation 2017-09-07 Summary Introduction... 3 Access... 3 Base URL... 3 Europe hosting... 3 Asia hosting... 3 Authentication... 3 Single call... 4 Bulk call... 4 Transactional messages...
More informationTelenor Corporate Call & SMS. API Documentation
Telenor Corporate Call & SMS API Documentation Table of Contents 1. Authentication & Session ID... 1 2. Sending a Quick Message... 2 3. Query a Quick Message... 3 4. Create a Subscriber List... 4 5. Add
More informationSophisticated Simplicity In Mobile Interaction. Technical Guide Number Information Services - Asynchronous SOAP. Version 1.3
Sophisticated Simplicity In Mobile Interaction Technical Guide Number Information Services - Asynchronous SOAP Version 1.3 Table of Contents Page 1. Introduction to Number Information Services 3 2. Requirements
More information2. On completing your registration you will get a confirmation . Click on the link or paste the link into your browser to validate the account.
Bongo Live SMS API v1.4 Revision History: v 1.1 - Initial Release. v1.2 19/6/2013 - Added Balance check and Sender Name Check v1.3 15/10/2013 Added incoming sms specifications v1.4 13/05/2014 Added API
More informationPRE BID REPLIES FOR NPCI:RFP: /0020 DATED RFQ FOR SMS GATEWAY SERVICES FOR INTEGRATION WITH FRM SOLUTIONS
PRE BID REPLIES FOR NPCI:RFP:2012-13/0020 DATED 27.11.2012 RFQ FOR SMS GATEWAY SERVICES FOR INTEGRATION WITH FRM SOLUTIONS SR.No Document Ref Page No Clause No Description in RFQ Clarification Sought Addittional
More informationWebSMS 5.0. User Guide. June 2011
WebSMS 5.0 User Guide June 2011 Revision History Version Date Version History 3.0 Apr, 21 2010 Document Released 3.1 Jun, 22 2010 Updated some screen shots 4.0 Aug, 5 2010 Added the following features
More informationSONERA OPERATOR SERVICE PLATFORM OPAALI PORTAL SMS. FREQUENTLY ASKED QUESTIONS, version 2.0
SONERA OPERATOR SERVICE PLATFORM FREQUENTLY ASKED QUESTIONS, version 2.0 OPAALI PORTAL Q: Why Registration link to Opaali portal does not work currently, HTTP Operation Forbidden error is shown? A: Sonera's
More informationTS V6.1.0 ( )
Technical Specification Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS); Point-to-Point (PP) (GSM 03.40 version 6.1.0 Release 1997) GLOBAL
More informationmvaayoo API Ver 1.2.0
Ver 1.2.0 DOCUMENT RELEASE NOTE Ver 1.2.0 Author(s): Sriram Gopal Reddy K Date: 21/10/2009 Reviewer(s): Dipto Mukherjee Date: 21/10/2009 Approved by: Date: REVISION HISTORY Document No: Document Title:
More informationWhatsATool API - REST-Like Interface to WhatsATool Services
Disclaimer This service and also mtms Solutions GmbH is not associated in any case with WhatsApp. WhatsApp is a registered Trademark owned by WhatsApp Inc. mtms is not related in any way with WhatsApp
More informationWAM!NET Submission Icons. Help Guide. March 2015
WAM!NET Submission Icons Help Guide March 2015 Document Contents 1 Introduction...2 1.1 Submission Option Resource...2 1.2 Submission Icon Type...3 1.2.1 Authenticated Submission Icons...3 1.2.2 Anonymous
More informationSMS4BD Gateway Integration
SMS4BD Gateway Integration TECHNICAL DOCUMENTATION v3.0 This document is intended to help IT experts in integration of SMS gateway of SMS4BD. Any alteration of this document without permission is strictly
More informationImplementation Guide for Delivery Notification in Direct
Implementation Guide for Delivery Notification in Direct Contents Change Control... 2 Status of this Guide... 3 Introduction... 3 Overview... 3 Requirements... 3 1.0 Delivery Notification Messages... 4
More informationMy MessageMedia User Guide
My MessageMedia User Guide Copyright and Trademark Statement 2011 MessageMedia All rights reserved. Apart from any use permitted under the Copyright Act 1968, no part of this publication may be reproduced,
More informationFax Broadcast Web Services
Fax Broadcast Web Services Table of Contents WEB SERVICES PRIMER... 1 WEB SERVICES... 1 WEB METHODS... 1 SOAP ENCAPSULATION... 1 DOCUMENT/LITERAL FORMAT... 1 URL ENCODING... 1 SECURE POSTING... 1 FAX BROADCAST
More informationExtended sms2 API Documentation
Extended sms2email API Documentation Written by Jateen Mistry Revised: 19 th April 2004 Description The advanced sms2email API is an extension to publicly available messaging API. The existing API is concerned
More informationCHANGE REQUESTS TO. GSM 03.40, on Enhanced diagnostic Information for SM-MT GSM 04.11, 04.13, 07.08, on Introduction of RP-ACK User data
Tdoc SMG 054/97 ETSI TC SMG Paris, France 10-14 February 1997 Source: SMG4 CHANGE REQUESTS TO GSM 03.40, 09.02 on Enhanced diagnostic Information for SM-MT GSM 04.11, 04.13, 07.08, 09.02 on Introduction
More informationSMS for REST Professional
RockendSMS Enhanced Integration SMS for REST Professional RockendSMS has newly designed and developed an upgrade to the way you send SMS through REST Professional V14 and above (RockendSMS Enhanced Integration).
More informationQuick help quide to GSM PDU mode structure
1 (6) Quick help quide to GSM 07.05 PDU mode structure AT+CMGS Send Message Sends a message from the DTE to the network (SMS-SUBMIT): AT+CMGS=PDU The length of the actual
More informationConfiguration Tasks. Configuring the System Using CLI Commands. Configuring the System Using the GUI
Last Update: June 28, 2007 This chapter lists the tasks for configuring and maintaining Cisco Unity Express and contains the following sections: Configuring the System Using CLI Commands, page 21 Configuring
More informationMessage Networking 5.2 Administration print guide
Page 1 of 421 Administration print guide This print guide is a collection of system topics provided in an easy-to-print format for your convenience. Please note that the links shown in this document do
More informationUSER GUIDE. EBMS SECURE MailGate
USER GUIDE EBMS SECURE EMAIL MailGate USER REGISTRATION When a secure email is sent to a new user, Secure Mailbox generates a notification and sends it to their email account. The notification contains
More informationAPI HTTP TECHNICAL DOCUMENTATION WEB-BASED SMS SENDING PLATFORM. Version Update: July 12th Mobile Marketing and Messaging Solutions
Mobile Marketing and Messaging Solutions WEB-BASED SMS SENDING PLATFORM API HTTP 12/05/2015 1:50PM Hello. Your order ref: 123456 is ready for pickup at your Relay Point 10 Amiens Street, 75002 Paris. Please
More information